Quoting Carsten Hey ([email protected]): > Christian, orphaner has been forked, see #414865. I CC'd you because I'm > interested in your views regarding forks and l10n issues, since you are very > experienced in the latter. > > Translators will probably need to do double work since most strings are > currently the same. The textdomain changed, but I think this could be adapted > if required. I could add the strings needed by the fork to orphaner to > minimize the required translation work or give Christophe write access to the > repository, so that he is able to add these strings himself. The fork could > merge the po files from time to time from the public svn repository. What do > you (both) think?
I'm missing the backgroung of this but I can at least mention that, yes, merging strings from one package/software to another is fairly easy, at least techniall speaking: msgcat --use-first project1/po/xx.po project2/po/xx.po new/xx.po msgmerge -U new/xx.po project2/po/project2.pot (assuming that project1 is the "reference" one and project2 is the target one...."xx" is to be looped over all languages supported in project1) When you start project2, you just indeed copy all PO files from project1 and then "msgmerge" them with the new POT file for project2. Of course, later on, it is highly recommended to keep the same set of translators. Also, if, in yur fork you get new translations for new languages, it would be considered good practice to send them back to the originating project, if both continue to share strings.
signature.asc
Description: Digital signature
