> > ... > Good questions. > > In big project using third party packages you will easily get value > > clashes. And the same value must be translated differently depending > > on the context. So merging would be fatal. > > I'm not sure, how the lcltranslator should know, where to lookup up > > the translations for each unit. Maybe the IDE should create lists > > which unit belongs to which package/project and put this for example > > into an include file. > > > > > > > Is some languages are already translated how should that be handled? > > > > There is the tools/updatepofiles tool. It is not yet integrated > > into the IDE. > > Has anybody ideas, suggestions, remarks? >
Just a taught, maybe we could store the translation String in the .po as msgid "FORM1.LABEL1.Caption=hello I'm Luis" msgstr "Ola eu sou o luis" then the LRSTranslator would search for the translation of "FORM1.LABEL1.Caption=hello I'm Luis" and not "hello I'm Luis". With ths solution we would never the problem of value clashes. I also don't think it would create a problem for the translators. Would also have to find a solution of the .rst conversion since this one is only good for the forms. _LR_ > > Mattias > > _________________________________________________________________ > To unsubscribe: mail [EMAIL PROTECTED] with > "unsubscribe" as the Subject > archives at http://www.lazarus.freepascal.org/mailarchives _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
