RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Gimp-docs Digest, Vol 48, Issue 11

This discussion is connected to the gimp-docs-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 4 messages available
Toggle history

Please log in to manage your subscriptions.
mailman.3.1211828406.10374.... 07 Oct 20:29
  Gimp-docs Digest, Vol 48, Issue 11 Vitaly Lomov 30 May 20:46
   Gimp-docs Digest, Vol 48, Issue 11 Sven Neumann 02 Jun 22:02
    Gimp-docs Digest, Vol 48, Issue 11 Marco Ciampa 03 Jun 01:07
Vitaly Lomov
2008-05-30 20:46:28 UTC (almost 17 years ago)

Gimp-docs Digest, Vol 48, Issue 11

I believe Nickolay Shmyrev used gettext for menu translations for russian. I did a bit of translation as well and have to say it's annoying to translate one sentence at a time - you lose context of narative. This way the flow of speech on the accuracy of english version. One paragraph at a time is better (that's what the previous discussion talked about) but then it got into a stage when a single character change in english invalidates other translations. Last time I heard before it died off was using 'fuzzy' to marked changes (I don't quite know how that works)
Vitaly.

Sven Neumann
2008-06-02 22:02:56 UTC (almost 17 years ago)

Gimp-docs Digest, Vol 48, Issue 11

Hi,

On Fri, 2008-05-30 at 19:46 +0100, Vitaly Lomov wrote:

I believe Nickolay Shmyrev used gettext for menu translations for russian. I did a bit of translation as well and have to say it's annoying to translate one sentence at a time - you lose context of narative. This way the flow of speech on the accuracy of english version. One paragraph at a time is better (that's what the previous discussion talked about) but then it got into a stage when a single character change in english invalidates other translations. Last time I heard before it died off was using 'fuzzy' to marked changes (I don't quite know how that works)

The tools will mark the translations as fuzzy when the original message changes slightly. A fuzzy translation is not going to be used (it will be treated as untranslated), but it is relatively easy for the translators to follow the changes in the original message and to remove the fuzzy marker.

Sven

Marco Ciampa
2008-06-03 01:07:07 UTC (almost 17 years ago)

Gimp-docs Digest, Vol 48, Issue 11

On Mon, Jun 02, 2008 at 10:02:56PM +0200, Sven Neumann wrote:

On Fri, 2008-05-30 at 19:46 +0100, Vitaly Lomov wrote:

One paragraph at a time is better (that's what the previous discussion talked about) but then it got into a stage when a single character change in english invalidates other translations. Last time I heard before it died off was using 'fuzzy' to marked changes (I don't quite know how that works)

The tools will mark the translations as fuzzy when the original message changes slightly. A fuzzy translation is not going to be used (it will be treated as untranslated), but it is relatively easy for the translators to follow the changes in the original message and to remove the fuzzy marker.

yeah and using kbabel, poedit or emacs, for example, is easy to jump directly to the fuzzy or untraslated strings. Updating the paragraphs is straightforward using the gettext package utils: you can easily discover what is changed and so is really quick to find and fix.

bye