Looking into it further I have looked at the Analyze output and the diagnostic print out had the text from [1] preceded by a line GetBuddies() returned dbus ....
where GetBuddies() is a procedure name in the program which is invariant in different languages On that basis, it makes more sense not to translate 'Buddy' in [1] so its relationship to the previous diagnostic line is more obvious Tony > Hi Samy, > > On 17 Sep 2011, at 23:04, samy boutayeb <s.bouta...@free.fr> wrote: > > > Hi again, > > > > In the activity Analyze, I wanted to localize a few mixed strings, where > > it is difficult to decide where is the translatable text and the > > untranslatable variable. > > > > For instance, in [1]: > > > > Calling <Buddy %s>.GetJoinedActivities() > > > > or in [2]: > > > > <Buddy %(path)s>.GetProperties() -> %(props)r > > > > My guess is that in [1] one should translate "Calling" and "Buddy", and > > in [2], one should only translate "Buddy". > > > > could someone confirm what is translatable in those strings? > > Yes you guess is correct. Analyse is an interesting case regarding > translation as it does output so much technical text information, hard to > know where to start with adding #TRANS comment hints ;) > > Regards, > --Gary > > > TIA > > samy > > > > > > _______________________________________________ > > Sugar-devel mailing list > > Sugar-devel@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > _____________________________________________________ > This mail has been virus scanned by Australia On Line > see http://www.australiaonline.net.au/mailscanning _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
