Contributions are always welcome. Just send patches and comments to 
rburns@softhome.net. I'm especially partial to localizations. You 
don't have to know how to program to do that. But, it isn't exactly 
straightforward, either. You need to do the following steps.

1. create your <language>.lproj directory inside the Poe/Resources/Shared
   directory.

2. copy the CommentInfo.strings file from one of the pre-existing 
   .lproj directories to your newly created one. This file contains the
   localized titles for the vorbis comment tags, and their
   descriptions. make sure you don't get the CommentInfo.plist file,
   by mistake. Changes to it might inadvertantly cause terrible things
   to happen.

3. run make_strings from the Poe/Resources/Shared directory - like so:
   
   make_strings -L "<language>" ../*.m

   you will get some errors, but a localizable.strings file should
   be in your <language>.lproj directory when it is finished.
   good documentation for make_strings can be found in the GNUstep
   source distribution in core/base/tools/make_strings/Using.txt

4. Now you will have two .strings files in the .lproj directory. Poe uses 
   gorm files for its interface, though they don't need to be edited for the
   purpose of localization. All the localizable strings in the program
   can be translated from these two files.

5. translate the text in CommentInfo.strings. this can be done in a 
   text editor.

6. translate the text in Localizable.strings. this can be done in a 
   text editor as well.

7. If your language contains non-ascii characters, you will need to run
   cvtenc on the two previous files*, when you are finished - like so:

   cvtenc -EscapeOut YES Localizable.strings > TempLocalizable.strings
 
   If the new files look ok when you are done, rename them to their 
   orginal names. (they should have any non-ascii characters replaced
   with a unicode escape sequence)

That should be it. If you have to go back and do further modifications 
to the *.strings files, after you have run cvtenc. you should first convert 
the strings file back to your native encoding, like so:

cvtenc -EscapeIn YES Localizable.strings > TempLocalizable.strings

edit TempLocalizable.strings, and then convert it back to ascii, just as 
you had done before. like this:

cvtenc -EscapeOut YES TempLocalizable.strings > Localizable.strings


*GNUstep should have support for utf-8 strings files now, though I've had 
mixed results in my use. When using utf-8 encoded files, all that conversion 
mess is unnecessary.



 


