El dv 14 de 08 de 2009 a les 16:18 +0800, en/na Ray Wang va escriure: > 2009/8/14 Aron Xu <[email protected]>: > > Hi, > > I am doing translations on Simplified Chinese, it's true that we cannot > > avoid duplication of effort sometime. What's more important, many > > translators prefer doing such work on platforms such us launchpad.net > > rather than just facing the original po files, because they think using a > > web interface can be more convenient and don't need to care about merging > > pot, check file format, etc. But the problem is also there as everyone > > knows, it's difficult for translators to control the quality because it's > > not easy to keep only specified persons working on specified files in the > > same time up to now. So we cannot using the files from it directly. > > Upstream translators have to review everything if he/she wants to make them > > into our upstream translation. Since translating GNOME is a huge project, > > that's not very easy to avoid all of the shortcomings: duplication of > > effort, difficulty on quality assurance, wider participation on upstream > > work. We have to lose some of them when we make any decision on means of > > working. > > > > Having a Web translation tool is Great! It ease the process, and you > don't have to be worried about much other than the quality, > limit the people who have rights to modify the msgstr might be a workaround?
Sure, reducing the number of people who has rights help, but to have good translations, not only is necessary to ensure a quality, but also consistency across them and within a single translation. What if more than one translator use different translations for "File"? You will end up with file open dialogs with different translations on the title, on the menus, etc .. Cheers, > > Aron > > > > On 2009-08-14,"Claude Paroz" wrote: > >>Le mercredi 12 août 2009 à 22:19 -0600, Stormy Peters a écrit : > >> > >>> Collaboration among advisory board members: Now that we have a sys > >>> admin team in place would like to find ways that we can collaborate > >>> better. Mentioned an article by J5 that talked about that RH, Novell > >>> and others are less involved because of the maintenance burden.They > >>> spend time on money on things like translations. No process to get > >>> them upstream and so they do it all over again next year. > >>> > >>> Ideas for collaborating between advisory board members: > >>> 1. Translations. > >> > >> > >>Hi Stormy, > >>Thanks for this interesting report. I was a little surprised by the part > >>about translation. Where are those translators ? Our i18n process is > >>completely open, so I don't understand why they do not contribute > >>upstream in the first place. > >>Would be great to have more details about this issue. > >> > >>Cheers, > >> > >>Claude > > > > ________________________________ > > 没有广告的终身免费邮箱,www.yeah.net > > _______________________________________________ > > foundation-list mailing list > > [email protected] > > http://mail.gnome.org/mailman/listinfo/foundation-list > > > > > > -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net _______________________________________________ foundation-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/foundation-list
