En/na Stefano Canepa ha escrit: > Il giorno dom, 01/01/2006 alle 14.47 +0100, Emanuele Aina ha scritto: >>I think that keeping the translated part well separated from the >>language specific one would make life easier for the translators. >>Mixing and matching them will create confusion and many troubles... Could you explain why? I thought translators only need to deal with the well defined list of pages we all will decide that need to be translated in other languages. Translators dont need to deal at all with language specific content because there is nothing to translate there. On the other hand, the primary goal should be to make life easier to users, and the main way to do this is offering a solid and sensible structure and navigation when moving into a language. They don't need to know if this page is translated or genuine, isn't it? >>A good separation could be: >> >>*.gnome.org -> simple translation of the contents >>it.gnome.org -> language specific contents (maybe translatable >>themselves, at least the main page in english) gnome.org/it/volare.html and it.gnome.org/volare.html can be just the same pages, this falls into the aesthetic factor. For consistancy we should choose and use one. What would be the Italian equivalent of foundation.gnome.org? > I think this is the best solution, leaving each local group create their > content in their language. We need to be careful with the difference between locales and local groups. In the Italian example both locale and local almost fit, but other languages may have many local groups and also some local groups may have many languages. There is no big problem, though. The concern is that locale speakers and local groups have autonomy to create their own content and interactive spaces once they have translated/localised the agreed common content. This can be done. -- Quim Gil - http://desdeamericaconamor.org
Attachment:
signature.asc
Description: OpenPGP digital signature