Hi again, We all know that encounter of constrains in translation is natural. But we have to look the root cause of the problem. I think that basically such problem arise due to two reasons. 1. Due to different rule of two languages like Rui pointed out on gender issue or use of a word with same form in Noun and Verb like save, print, report etc. ( Language rule: the root cause of problem!) 2. Use of a particular word with multi or dual meanings in many places as a message like 'none' , 'on' or 'off' etc. though there exists suitable alternate word (the writer i.e. man: The root cause of the problem!). My immediate concern is for the second category. I think that for the first case, it should be addressed differently. For the second case, it is easy if the code developer keep few things in mind before writing a word/phrase inside the double quotation marks as message for the user. Take an example: a) The word 'none' in the selection list of voices be written as 'no choice' b) Capslock/Scroll/Numpad key be said 'locked/unlocked' instead of 'on/off' In gist; the second category problem be completely eliminated if avoidance of repeated message text adopted and specific suitable words are used. Him p. Gautam On 9/8/12, Mesar Hameed <mesar.hameed@xxxxxxxxx> wrote: > Hi, > > You are right, and we have a ticket for this work here: > http://www.nvda-project.org/ticket/1524 > > @jamie, the translation workflow already uses msgfmt msgmerge, and not the > po files. > Might you have some time to look at the needed code changes? > Sorry I am currently snowed under. > > Thanks, > Mesar > On Sat 08/09/12,18:57, Him Prasad Gautam wrote: >> Dear All, >> Are you also getting the same nature of problem as below? >> Either yes or no, let you give your opinion…. >> >> As a translator, I am questioned by some ne locale users regarding the >> inappropriateness translation of some 'multi meaningful English word' >> messages like 'on' or 'off'. As we all know that these words are used >> in many but entirely different situational cases e.g. >> Caps/Scroll/Numlock key: on/off, AC line: on/off, Mouse tracking: >> on/off and many things can be said by the same word of 'on/off'. It >> is appropriate for English but the same does not apply to other >> language. In Nepali, there exists no a single word which may be used >> to express the situation of a key on a keyboard and state of the >> supply of the electricity! Just to address different conditional >> states of different messages, like msgid "on" or msgid "off" are a >> great headache and seriously challenge the quality of the translator. >> What to do if a common word fit for all such messages does not exits >> in own language? Instead if the developer use the word something >> like 'locked/unlocked' for keys of a keyboard, >> 'connected/Disconnected' for power supply, 'yes/no' for mouse tracking >> and so on; there would no problem of looking an appropriate words for >> translators! >> >> I request James and Mesar to pay an attention in this issue and make a >> strict policy of using specific word for message instead of using a >> common English word (like on/off) unless an alternate specific >> English vocabulary exists. Definitely, this concept increases the list >> of messages to be translated but additional work for just few more >> words is not that much burden. Present list of 1129 message may be >> 1200, so what? it will be easily translated but in a flexible >> environment for choosing an appropriate words! This will increase the >> quality of translation. >> >> >> Him Prasad Gautam >> Kathmandu, Nepal > > -- Him Prasad Gautam Kathmandu, Nepal