Re: [native-lang] Status update season!
On 15/12/2006, at 6:27 PM, Muguntharaj Subramanian wrote: Hi Charles, This update from Tamil Team. We havent done much. But have started becoming active. 1. We have started submitting language files(even though thye are not complete) regularly on time starting from OOo 2.0.3 onwards. So we do have OOo2.1 build for tamil. snip Congratulations to the Tamil team on their progress! :) I have found these update reports to be really fascinating, a look behind the scenes of the different language projects. Could we perhaps maintain a wiki page that summarized current status for each project? Or perhaps link from Rafaella's new stats page: http://wiki.services.openoffice.org/wiki/Translation_Statistics each language name being a link that leads to a separate page, in English, briefly summarizing the current status of each project? Quite apart from general interest, I think there would be people who don't speak the local language, but could want to know the status of localization of OOo for that language: business networks, educational and other development organizations, and our l10n and NLP co- ordinators. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part
Re: [native-lang] Status update season!
On 15/12/2006, at 8:17 PM, Charles-H.Schulz wrote: I strongly suggest we have a basic Howto for l10n projects. It doesn't need to be long and complex, but it can include items like: This page that I wrote not such a long time ago seems to answer some of your needs, but more needs to be added to it: http://wiki.services.openoffice.org/wiki/NLC What do you think? It's a good NLP introduction, Charles. I think I sort of fell through the cracks, taking over an established NLP level 2 project, but having nobody left to tell me what to do. If it happened to me, it might happen to others. So I suggest making a general l10n page similar to yours, based at l10n.openoffice.org but also linked from your page, which summarizes the steps needed to participate in a language project. The reason I stress l10n is that translators entering the OOo project, if they have worked in other projects, are familiar with l10n and will be looking for i18n or l10n. NLP at that stage won't mean anything to them. The l10n page can introduce the OOo terminology. We do need an intro page which provides the type of information other translators are used to, if we want to attract them. If we make it clear that _every_ translator has to sign the JCA, for example, and join certain key lists and read key information, that will help. Then we need to extend your page, with one that shows the steps for achieving a released translation. The QA page, Release Action List for QA [1], is good, but how is a translator supposed to find it? If we link to it from l10n and NLP, we're making more effective use of our existing information. See the GNOME Translation Project wiki page [2], a very basic page which yet includes most things a new translator or language-team lead needs to know. We send every new translator there: it saves a lot of repeated explanation. Because the OpenOffice.org project is so large and diffuse, we need to have even more effective overall information processes than single projects, to pull the whole together, and give each part the access and abilities it needs. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://wiki.services.openoffice.org/wiki/Release_Action_List_for_QA [2] http://live.gnome.org/TranslationProject PGP.sig Description: This is a digitally signed message part
Re: [native-lang] Status update season!
Hello Clytie, Clytie Siddall a écrit : What do you think? It's a good NLP introduction, Charles. I think I sort of fell through the cracks, taking over an established NLP level 2 project, but having nobody left to tell me what to do. right. And besides it was geared towards you but to new NLP leads. If it happened to me, it might happen to others. So I suggest making a general l10n page similar to yours, based at l10n.openoffice.org but also linked from your page, which summarizes the steps needed to participate in a language project. Indeed. But it is not up to me to do that. Perhaps Rafaella would be interested in drafting a similar page as (http://wiki.services.openoffice.org/wiki/NLC) but for L10N? The reason I stress l10n is that translators entering the OOo project, if they have worked in other projects, are familiar with l10n and will be looking for i18n or l10n. NLP at that stage won't mean anything to them. The l10n page can introduce the OOo terminology. We do need an intro page which provides the type of information other translators are used to, if we want to attract them. If we make it clear that _every_ translator has to sign the JCA, for example, and join certain key lists and read key information, that will help. Then we need to extend your page, with one that shows the steps for achieving a released translation. The QA page, Release Action List for QA [1], is good, but how is a translator supposed to find it? If we link to it from l10n and NLP, we're making more effective use of our existing information. Yes, now it's all about connection:-) . I'll link some these pages to the NLC wiki. Perhaps some stuff on the QA and L10N pages could be necessary as well. See the GNOME Translation Project wiki page [2], a very basic page which yet includes most things a new translator or language-team lead needs to know. We send every new translator there: it saves a lot of repeated explanation. Ah, I beg to differ here. I browsed their site. Not only is it fairly slow to load, but I just don't find it clearer than the one of OOo. Of course it looks different and structures are different as well, but that really is not more understandable, at least to me Because the OpenOffice.org project is so large and diffuse, we need to have even more effective overall information processes than single projects, to pull the whole together, and give each part the access and abilities it needs. :) +1... Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[native-lang] Main Page - maybe translate it?
Hey! I tried to imagine that I am an entrepreneur who does not know English. I enter www.openoffice.org and see Native Language leading to native projects. But if I do not know English, I leave the web page convinced that I am not able to find the language version of OpenOffice.org that suits me. That is why I thought about a language picker. I have made one for Polish Project leading to other language projects. I could paste the code if needed. Konrad -- http://www.mojpiotrkow.pl/ Mój przyjazny portal http://www.konrad.stobiecki.pl/ Moja przyjazna strona domowa http://www.openoffice.org/ Mój przyjazny pakiet biurowy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] Status update season!
I would look into providing a sort of check list: all major steps you need to perform to have a localized OOo product which can be distributed. What do you think? I strongly agree to that. Maybe we can work that out on a Wiki page together. Erdal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] Status update season!
Rafaella, Rafaella Braconi a écrit : Hi Charles, Clytie and All, I'll be more than happy to work on a better overview for the localization process. Instead of documentation - which I think we do have - I would look into providing a sort of check list: all major steps you need to perform to have a localized OOo product which can be distributed. This is exactly what we need. All this made me realize that it is not because the info is somewhere on the site that it is accessible for everybody, especially for the newcomers, so clarity and pedagogy should be our concern... Best, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] Main Page - maybe translate it?
On 17/12/2006, at 1:43 AM, Konrad Stobiecki wrote: Hey! I tried to imagine that I am an entrepreneur who does not know English. I enter www.openoffice.org and see Native Language leading to native projects. But if I do not know English, I leave the web page convinced that I am not able to find the language version of OpenOffice.org that suits me. That is why I thought about a language picker. I have made one for Polish Project leading to other language projects. I could paste the code if needed. I have already mentioned this on dev@website.openoffice.org. I agree that it's a key point in accessibility for OpenOffice.org. In particular, if you don't use the same alphabet as the main page, without the language codes, flags or some kind of conventional language picker, you are completely lost. Imagine if the page were in an alphabet you can't read at all: Arabic, Chinese, Thai, Ogham. You wouldn't understand a single word of the page. That's where symbols, like language codes and flags, in a conventional language bar or language picker as expected online, makes such a difference. As a minor example, please see the language bar used on this wiki page: https://wiki.ubuntu.com/UbuntuWomen I have copied this reply to the [EMAIL PROTECTED] list. Could we have some action on this matter, please? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part
Re: [native-lang] Status update season!
On 17/12/2006, at 2:07 AM, Rafaella Braconi wrote: Hi Charles, Clytie and All, I'll be more than happy to work on a better overview for the localization process. Instead of documentation - which I think we do have - I would look into providing a sort of check list: all major steps you need to perform to have a localized OOo product which can be distributed. GREAT idea, Rafaella! :) And the checklist could link different steps to the more detailed docs. I don't think there's anything wrong with our docs, just that we don't necessarily know they're there or how to find them. We need overview statements, linked to the main pages, which then link us to the various support docs. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part
