SF.net SVN: avogadro: trunk/avogadro/i18n/avogadro_fr.ts

Can we translate one, copy the file, then translate what’s left? That
should be easy. I mean, if you copy the file, it will pick and choose
what you translate. Else we can just combine them for now… my bad.


Donald

(Tue, Sep 18, 2007 at 11:42:50PM -0700) benoitjacob@users.sourceforge.net:

Revision: 671
http://avogadro.svn.sourceforge.net/avogadro/?rev=671&view=rev
Author: benoitjacob
Date: 2007-09-18 23:42:49 -0700 (Tue, 18 Sep 2007)

Log Message:

Quite complete french translation of the app, I only left out GAMESS and
some chemical stuff I don’t understand.

I don’t translate libavogadro because there is so much redundancy
between libavogadro*.ts and avogadro*.ts that it amounts to doing twice
the same work. Quite frustrating, a solution must be found at the level
of the source code.

Modified Paths:

trunk/avogadro/i18n/avogadro_fr.ts

This was sent by the SourceForge.net collaborative development platform, the world’s largest Open Source development site.


This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


Avogadro-updates mailing list
Avogadro-updates@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-updates

Well, I don’t know much about the translation system, so can’t tell what
will work, what won’t, and what we should do.

But yes, I get what you mean, it seems to make sense in the short-term
until a full solution is found. By a full solution I mean that there
should not be redundancy between the two .ts files.

Cheers,
Benoit

On Wed, 19 Sep 2007, Donald Ephraim Curtis wrote:

Can we translate one, copy the file, then translate what’s left? That
should be easy. I mean, if you copy the file, it will pick and choose
what you translate. Else we can just combine them for now… my bad.


Donald

(Tue, Sep 18, 2007 at 11:42:50PM -0700) benoitjacob@users.sourceforge.net:

Revision: 671
http://avogadro.svn.sourceforge.net/avogadro/?rev=671&view=rev
Author: benoitjacob
Date: 2007-09-18 23:42:49 -0700 (Tue, 18 Sep 2007)

Log Message:

Quite complete french translation of the app, I only left out GAMESS and
some chemical stuff I don’t understand.

I don’t translate libavogadro because there is so much redundancy
between libavogadro*.ts and avogadro*.ts that it amounts to doing twice
the same work. Quite frustrating, a solution must be found at the level
of the source code.

Modified Paths:

trunk/avogadro/i18n/avogadro_fr.ts

This was sent by the SourceForge.net collaborative development platform, the world’s largest Open Source development site.


This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


Avogadro-updates mailing list
Avogadro-updates@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-updates


This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Am Mittwoch, 19. September 2007 10:09:26 schrieb Benoit Jacob:

Well, I don’t know much about the translation system, so can’t tell what
will work, what won’t, and what we should do.

But yes, I get what you mean, it seems to make sense in the short-term
until a full solution is found. By a full solution I mean that there
should not be redundancy between the two .ts files.

There is this catalogue-feature thing. Not 100% sure but I think with that you
can add strings to a “Database”. When you translate a new file this database
is used to auto-translate fitting strings. Then you just need to “ok” these
strings.

For linguist this seems to be called Phrasebook. I just used the german
phrasebook, it autotranslated 11 entries. If we move all phrases from Avo to
a avo-phrasebook and use that book to translate libavo the issue is solved.

BUT I have no idea how to move all those strings into a phrase book. It seems
you need to do that by hand which would take ages…

Carsten

Am Mittwoch, 19. September 2007 09:25:38 schrieb Donald Ephraim Curtis:

Can we translate one, copy the file, then translate what’s left? That
should be easy. I mean, if you copy the file, it will pick and choose
what you translate. Else we can just combine them for now… my bad.

Would Kalzium use the translations we do for libavo or would it have to
translate it itself…? I don’t know about the i18n internals of KDE/Qt…

If it has to do a second translation anyway I see no point in having two
translationfiles for Avo/Libavo…

Carsten

On Wednesday 19 September 2007 10:30:53 Carsten Niehaus wrote:

Am Mittwoch, 19. September 2007 09:25:38 schrieb Donald Ephraim Curtis:

Can we translate one, copy the file, then translate what’s left? That
should be easy. I mean, if you copy the file, it will pick and choose
what you translate. Else we can just combine them for now… my bad.

Would Kalzium use the translations we do for libavo or would it have to
translate it itself…? I don’t know about the i18n internals of KDE/Qt…

If it has to do a second translation anyway I see no point in having two
translationfiles for Avo/Libavo…

Carsten

I take it that Kalzium will just use libavogadro and libavogadro will use its
own translations, so that Kalzium won’t even see the libavogadro strings.
Well, there will always be the Kalzium-specific strings just like there are
the avogadro-specific strings. But for sure we should move as many strings as
possible “upstream”, that is, in libavogadro, so that we only need to
translate them once there and then all apps benefit from that single
translation.

Benoit

Am Mittwoch, 19. September 2007 10:35:32 schrieb Benoît Jacob:

On Wednesday 19 September 2007 10:30:53 Carsten Niehaus wrote:

Am Mittwoch, 19. September 2007 09:25:38 schrieb Donald Ephraim Curtis:

I take it that Kalzium will just use libavogadro and libavogadro will use
its own translations, so that Kalzium won’t even see the libavogadro
strings. Well, there will always be the Kalzium-specific strings just like
there are the avogadro-specific strings. But for sure we should move as
many strings as possible “upstream”, that is, in libavogadro, so that we
only need to translate them once there and then all apps benefit from that
single translation.

We want Kalzium of KDE 4.1 use libavogadro (instead of the local copy).

Is the idea that the user just installs libavo, eg NOT Avogadro (split
packages) or will the user install Avogadro which also ships libavogadro?

In that case (bundled packages) there is no point having two translationfiles
anyway…

Carsten