I used to use RBE http://docs.ofbiz.org/display/OFBIZ/Plugins#Plugins-RBE http://docs.ofbiz.org/display/OFBIZ/Tips+for+translation for such tasks. I got some problems recently using it (with last version) but it's still the best tools for this kind of tasks even if in some case I still use the sandard Eclipse properties editor.
I'm not sure we want to do such a things but having an UI like in RBE is certainly a must when it comes to deal with several languages... Jacques De : "Vinny Miana" <[EMAIL PROTECTED]> > I think Jonathon expressed well what I meant. It would be really nice > to have translations side by side, > however it could be a maintenance nightmare to have more than 5 > languages. Even though version control > can deal with merging not having to merge is always helpful. Scrolling > down through the translations once > we have more than a few will be more time consuming than scrolling one > line per sentence to translate. RBE is great for that > Once think that would be nice is some tool that would tell one what > labels are missing in the resource file. RBE do that (parameter) > It could really help ensuring that a translation is complete and up to date. > > Did any of you guys take a look at the Commons Configuration? > I think if you are changing the handling of properties it is probably > a good idea of plugging that in. I hope Adrian will see this message since he seems to want to handle the task. > Vinny > > > > > > > > > > > On Nov 27, 2007 3:34 AM, Jonathon -- Improov <[EMAIL PROTECTED]> wrote: > > Seconding this. > > > > Having translations side by side is great. One XML element for one label is > > great, with that > > single element containing all the possible translations. Conversely, 10 XML > > elements for one label > > in 10 languages is difficult to maintain. > > > > Same concept applies to having a single file for a single set of labels. > > > > About merging problems for the single file, that's what version control is > > for. To facilitate > > multiple collaborative commits to a single set of codes (even a single > > file). > > > > Jonathon > > > > > > David E Jones wrote: > > > > > > On Nov 26, 2007, at 8:13 PM, Vinicius Miana wrote: > > > > > >> Hi all, > > >> > > >> I don't think having all the translations in one single file is a good > > >> idea: > > >> > > >> 1) If you do not want to have all translations on your system it is > > >> easier to erase them > > > > > > If you're trying to slim down OFBiz this is the least of your > > > problems.... These don't get very big anyway compared to other stuff in > > > OFBiz. > > > > > > This certainly makes it harder, I'm not arguing against that, but I > > > don't think this is as high on the list as other priorities. > > > > > >> 2) The person that speaks French is not necessarily the same that > > >> speaks Chinese. With one > > >> single file there will be more people working (committing/merging) the > > >> same file. > > > > > > Merging is generally only a problem if two changes happen on the same > > > line. > > > > > > -David > > > > > > > >
