On Сбт, 2006-06-10 at 15:11 +0200, Jan Kundrát wrote: > a) Translation of metadata.xml stuff in our tree (Is there any method to > keep them up-to-date when the English text changes? Something like > "revision" attribute that gets bumped when the English text gets updated?)
While we do not have "version" or "revision" attribute, just drop all translations whenever you update English. > c) l10n for other packages and sending patches upstream > d) Translation of manpages. man-pages-cs for example sucks :(. Do we really need to do this inside Gentoo i18n project? This tasks are common for many distributions and should be done outside Gentoo. So just translate and send translations upstream. > e) Translation of our documentation (that's the GDP's job, the intention > is just to "share human resources" :) ) and GWN. > > f) Translation/localization of w.g.o. Efforts were already started > (meaning that "the technology is available on at least one experimental > site). Opposed to c) and d) this requires organization inside Gentoo and thus requires i18n project. Fex, to increase the profit from translated GWN translated versions should come out together with English one. > e) Persuading people that having comments in configuration files > *without* an equivalent somewhere on the web is evil. Good example might > be baselayout. Why? Stuff on the web can be translated pretty easily, > configuration files can't. Personally I do not like idea to look at web for package documentation. There already exist decision to put all example files somewhere into /usr/share. I hope one day this happens and then all translated configuration files also can be put there. I think the main goal of i18n should be not translation but organization (at least at first time). Untranslated staff will always remain because devs have lack of time/interest and project can nothing to do with that. But people post bugs with translated metadata, translated documentation and to resolve them we need place to find the right devs for this. And i18n project is the right place to look for them. Peter.
signature.asc
Description: This is a digitally signed message part
