Re: Current status on migration to gettext/po

["Ulf-D. Ehlert" <ude88@xxxxxx>]

Hi Roman,

Roman Joost (Freitag, 5. September 2008, 14:19):
> The intendation is a bit messed up after the script splitted the
> languages, 

Yes, I skipped the empty text nodes which are caused by whitespaces 
between xml tags due to intendation and empty lines:
    <foo>
       <bar>

> but I think that it's something we don't have to care  about. 

'xml2po' would delete these empty texts anyway.

> For the migration, it's probably the most important step. 
>
> The migration would look like this now:
>
>     1. Merge the TRUNK into the Branch, to be up-to-date with the
> latest content.
>     2. Split the languages using Ulf's new python script.
>     3. Create the initial *.po files which already have English
>     original and translated strings.
>     ^---- dry run -----^
>     4. Check if we can continue working from this point
>     5. If 4. is true, than backmerge the branch into TRUNK
>     6. Continue to fix the translations and work on the documentation
>     for 2.6
>
> We can test if the points 1,2 and 3 work flawlessly and produce what
> we expect. If that works and we can use the migrated content (4.) we
> could merge our branch into TRUNK and continue using *.po files.
>
> Did I missed something?

Maybe:
  (a) I've made some changes to handle more XML tags. But there's still
      an essential part of the algorithm I had in mind but did not yet
      implement. This final / non-final stuff was just meant to simplify
      and speed up the script....
      Did you made some test with with xml2po's "reuse" feature? Are the
      results usable?
  (b) There are still some problems with unusual files, especially the
      glossary files. And what about the key-references?
  (c) I did not start to convert the Makefile to Makefile.am. (No, I'm
      not working 24h/day on gimp-help. ;-))
  (d) I think you wanted to release a new version based on the current
      (old) build system and the XML source in trunk. IMHO you should
      definetely do this before any serious attempts to migrate!
  (e) There is still a bug in xml2po (at least I considered it to be a
      bug - see http://bugzilla.gnome.org/show_bug.cgi?id=545478) and
      I'm using a patched version of xml2po. These two versions produce
      different po files. I'm not sure what to do here.

Ulf


_______________________________________________
Gimp-docs mailing list
Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs