2010/11/30 Rogier Wolff <[email protected]> > > > Allow me to learn.... > > > > So you have a tool that reads the new "to be translated" strings, > > and an old "translation table" (with e.g. EN -> NL translations). > > > > And It will see that for example a typo was fixed in the new "to be > > translated" table, so that the EN part from the old translation table > > no longer matches, but it matches "almost" so that it still finds it. > > So when the old translation table didn't have a translation for > > > > save panorama? > > > > but matches it to the old > > > > save panorma? -> Panorama opslaan? > > > > translation in the old translation table you loaded? > > > > correct? > > > > Roger. > > Yes and more. If you have for example: Could not open project file: -> Kan projectbestand niet openen:
and a new string gets added like: "could not open script : %s", then the program might suggest: "kan projectbestand niet openen: %s" or even "kan script niet openen: %s" That would only need a small change like "kan script: %s niet openen" and thereby saves you some typing and guessing. It's sometimes also spot on needing no change at all. If you use something like vi, what I use quite a lot, you don't have these options off course. So I use the best tool I know (for OSX): poedit Harry -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
