2013/6/12 Kadal Amutham <[email protected]> > I already completed major portion of translation. Another 1800 words left. > I am talking the problem of mine alone. This is problematic to all the > translators. Some time, same string is present in the same file itself. > > My aim is that there shall be only one set of strings, all over the AOO. It > may be used in many places under various conditions. I do not understand > why there is a need for same string repeated in many places. >
One thing that comes to my mind are hardcoded keyboard accelerators. AOO is able to generate keyboard accelerators automatically, but if you have, for example, the string "Save" and on one window the accelerator is on the "S" while on other is on "a" the user will find an inconsistency. That's why some common accelerators are coded with the original string, like "~Save"... but this of course cause an awful lot of other translation issues: "Guardar" do not have "S" and as translator it is not easy to choose a consistent set of accelerators without seeing the menu entry on its context, on which case one ends by not using accelerators at all. No idea how this can be handled, but I agree that translating dozens of short strings like "Save" 30 or more times each one is time consuming and boring. > > After completing my current translation, I want to study this problem Great! Regards Ricardo > > With Warm Regards > > V.Kadal Amutham > 919444360480 > 914422396480 > > > On 12 June 2013 19:27, Claudio Filho <[email protected]> wrote: > > > Hi > > > > 2013/6/12 Kadal Amutham <[email protected]>: > > > Then one can sort and find out how many repetitive sentences are > > available > > > and how to handle them > > > > Humm... Kadal, correct me, if i did some mistake, but your request is > > based in the same string many times in differents parts into > > translation, right? > > > > If yes, i strongly recommend you to use a translation tool like > > lokalize[1], part of KDE, where have a very nice resource: fill > > automatically the strings with 100% match. You can use what you > > already have translated as base form MT (machine translation), and if > > it find some string with 2 or more 100% match, it mark this string as > > fuzzy. > > [1]http://www.kde.org/applications/development/lokalize/ > > > > So, after this automated proccess, you need pass the strings, > > reviewing where is fuzzy (accepting or correcting) and giving a step > > up when is translated. > > > > If no, as Jurgen said, is possible to open a sdi file in Calc and play > > with it there. I did it 10 years ago (wow... i'm old..) :-p ;-) > > > > Bests, > > Claudio > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
