On Fri, 18 Feb 2005 22:26:31 +0200, David Fraser <[EMAIL PROTECTED]> wrote: > Pavel Jan�k wrote: > > > > > >What has to be done so this can be used? We have to keep the split of > >one msgid while upgrading PO files from new POT files, etc... David? > > > > > I'm not entirely sure how the oo2po / po2oo should handle this, but I > think they should handle it correctly because they'll use the source IDs > (the #: bit) to identify the strings. I don't have time to check now, so > if somebody wants to do this it shouldn't be hard to test :-) > > Let me know either way and I'll update the tools if neccessary >
If we are editing manually po-files only, question is how should msgmerge handle this when we are updating po-files with latest pot-files. I have tried this, kde-style msgids in po-s are of course not preserved, when in pot files strings are not unified, that means we should separate strings in pot file... as pot file is generated from sdf with every new milestone, it will be very annoying to do this manually every time ;) I will stay at my opinion, having the white-list (if this is possible to teach to translate-toolkit of course) with one addition: strings in list must be unified only in this case, when they are repeating in one pot file, eg. if word 'start' is in list and it appears in a pot file only once as whole string, it should stay with old msgid, if it is repeating in other pot file e.g. twice, then split should be done only in this pot file. -- Ain Vagula --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
