Re: [native-lang] New template project
Andre Schnabel írta: Hi Kami, KAMI schrieb: So let's start to work :o) For first step I will resort our templates info templates and templates-nonfree category.Templates category should contains LGPL or equivalent licensed materials. Subcategories remain untouched because they come from OpenOffice.org itself. I saw German language templates those uses different directory names. I think this is not a good thing on the way to uniforming template collection. I agree that this is very unfortunate but we have not been aware of the internal code structures, when we started to collect and sort the templates. At the moment our templates are used (redistributed) at other places, so we need to think a little before we resort the templates :-( Okay :o) But using the internal structures is the correct way .. I think, we would need to extend them. I'll work on that for our German template collection .. but this will take some time (speaking of weeks ). Well, I will be happy if you do this. Extending the current categories needs modifications in the source. I can do this, if we have a idea what are our requiments. We might try to push the modifications to the steam. Are there any proposal for this from your side? André KAMI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] Status update season!
Clytie, 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? Best, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] Status update season!
Robert, A very big thank you goes to Pavel, again, for all his help and patience. Indeed. My thanks also go to Pavel for his support of the localization and his work on the community builds. Thank you for this update, Robert, and keep on the good job! Best, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] Status update season!
Hi Charles and all, On 12/12/06, Charles-H.Schulz [EMAIL PROTECTED] wrote: And for everybody here on this list, I know you are all focused on the 2.1 release, but a status update on your project would be of course very nice! We have achieved more than 90% of translation in both GUI and Help. Our homepage http://ne.openoffice.org/ has been recently updated with the latest download links. But we are yet to see our spellchecker and thesaurus dictionaries integrated in OOo source. We are hoping that these would be there in 2.2. or 2.1.x. resolving the following issues: #i70512#, #i70513#, #i72094# with the inclusion for Nepali fonts in helpcontent2 auxiliary. Also, yet to fully learn about QA process ;) Cheers, Subir Nepali NL project Lead - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] Status update season!
Hello Subir, thanks for your work. This leads me to wonder what your Tibetan neighbours are up to. Could they also provide us with a status update? Also, yet to fully learn about QA process ;) OK. I think I should write a simple document together with the QA project. I hadn't realized, before Clytie and you, how difficult this QA process was... Thank you again for your contributions, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[native-lang] writing an easy QA howto
Hello, I'm calling for one-two QA member here to help me write a very short and synthetic howto on QAing the localized builds. As you have seen here on this list and according to the discussions on the NLC list, there is a need for a better explanation of our QA processes. Actually I even believe that newcomers should understand how QA fits in their work, and what they should do about it. More in-depth explanations can take place here, after the newcomers and QA testers have more or less been setup. Who would like to join me? I need somebody experienced for a one page document! Thanks, Charles-H.Schulz. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[native-lang] Translation Schedule for 2.2
Dear All, I know that many of you are still busy with the 2.1 release however due to the tight release schedules we have I would like to remind you of the release roadmap and the translation deadlines for the 2.2 release. For details please have a look at the message I posted yesterday at the [EMAIL PROTECTED] list. http://l10n.openoffice.org/servlets/ReadMsg?list=devmsgNo=7230 Apologies, if you have already received this message, but I just want to make sure you get this information so that you have enough time to organize the work on your side Kind Regards, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[native-lang] Re: [qa-dev] writing an easy QA howto
On 15 Dec 2006, Charles-H Schulz spake thusly:
Hello,
I'm calling for one-two QA member here to help me write a very short
and synthetic howto on QAing the localized builds. As you have seen
here on this list and according to the discussions on the NLC list,
there is a need for a better explanation of our QA processes.
Great idea! QA is a very important part of NL tasks, but not all
projects do (can do) QA.
--
Best regars,
Rail Aliev
http://{ru,tr}.openoffice.org
When your work speaks for itself, don't interrupt.
-- Henry J. Kaiser
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[native-lang] Re: [qa-dev] writing an easy QA howto
Hello Rail, Rail Aliev a écrit : On 15 Dec 2006, Charles-H Schulz spake thusly: Hello, I'm calling for one-two QA member here to help me write a very short and synthetic howto on QAing the localized builds. As you have seen here on this list and according to the discussions on the NLC list, there is a need for a better explanation of our QA processes. Great idea! QA is a very important part of NL tasks, but not all projects do (can do) QA. Right. And when it's time to think about it, they are lost :( Cheers, Charles. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] writing an easy QA howto
Hi Charles, Charles-H.Schulz wrote: Hello, I'm calling for one-two QA member here to help me write a very short and synthetic howto on QAing the localized builds. As you have seen here on this list and according to the discussions on the NLC list, there is a need for a better explanation of our QA processes. Actually I even believe that newcomers should understand how QA fits in their work, and what they should do about it. More in-depth explanations can take place here, after the newcomers and QA testers have more or less been setup. Who would like to join me? I need somebody experienced for a one page document! Sorry my precedent mail goes away without me reading this one. I'm willing to help you here. I'll begin through the week-end. Kind regards Sophie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [native-lang] writing an easy QA howto
On Fri, 15 Dec 2006 05:20:29 -0600, Charles-H.Schulz [EMAIL PROTECTED] wrote: Hello, I'm calling for one-two QA member here to help me write a very short and synthetic howto on QAing the localized builds. As you have seen here on this list and according to the discussions on the NLC list, there is a need for a better explanation of our QA processes. Actually I even believe that newcomers should understand how QA fits in their work, and what they should do about it. More in-depth explanations can take place here, after the newcomers and QA testers have more or less been setup. Who would like to join me? I need somebody experienced for a one page document! Thanks, Charles-H.Schulz. Here is a good parameter to write good documentation. If your kids read it and they don't understand, then that means that your documentation still need works to make it simpler. Another good parameter is having a '5 step program' to get the process understood. -- Alexandro Colorado Grupo de Usuarios Linux Tabasco http://www.gultab.org OpenOffice.org Community Contact // Mexico http://www.openoffice.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
