Re: [native-lang] Status update season!

2006-12-13 Thread Charles-H.Schulz
Soren,

thank you for your update. I actually thought that you had had the idea
of resigning, but left it aside. You did a very good job, and it's a
pity to see you go. But at least you're among us as long as nobody
showed up to take the lead :-) ... I'll keep you updated on the Faroese
and Greenlandish.

Best,
Charles.

Søren Thing Pedersen a écrit :
 Dear all
 
 Charles-H.Schulz skrev i dev@native-lang.openoffice.org:
 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!
 
 Good idea.
 
 Back in August after 3 years I signed off as NL lead on the Danish list
 and to Louis and Charles. However, I did not report it here on [EMAIL 
 PROTECTED]
 because I hoped the successor was soon found.
 
 The status from the Danish team is that the demanding part of
 translating the GUI and help to Danish is complete and easily
 maintained. Thus the effort is spreading to other areas.
 
 - Translation is as updated frequently by the team. I keep my website
 for translation updated and I still subscribe to dev@l10n.openoffice.org
 and this list to make sure the Danish localization is perfect -
 including the nitty gritty locale settings.
 - QA is managed by Thomas Roswall that along with his team triads RCs
 for bugs
 - Danish Newsletter is now edited by Leif Lodahl
 - Translation of documentation is also coordinated by Leif
 - An ISO image is maintained by Jørgen Kristensen. Jørgen sent all MPs a
 cd which caused a good public debate.
 
 Currently the main obstacle for the Danish end user is the lack of an
 included and good dictionary for spell checking. Various solutions are
 being discussed.
 
 The Danish team is looking for an active NL lead, Marcon and website
 maintainer.
 
 I stepped down for many reasons and mostly for positive reasons. The
 time was right - OpenOffice is now a completely valid alternative for
 Danish users - and personal stuff. It has been fun and demanding but
 mostly fun. It is good to leave when the project is doing great.
 
 Now, I freely roam the project as a less active contributor and
 issuezillian. Please don't hesitate to contact me. Thank you and see you
 around.
 
 Best regards
 Søren
 
 PS. Ping me if any Greenlandish or Faroese group wants help with the
 translation.
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[native-lang] Re: [discuss] RE: [ooo-announce] OpenOffice.org 2.1 Is Here

2006-12-13 Thread Mathias Bauer
Lovesh Vashist wrote:

 Hi Louis - Thanks for this update.
 
 I had recently very enthusiastically downloaded the then latest version of
 open office suite of products - fully aware that I will have to spend time
 to reorient myself away from MS Office suite of products. However, I was
 disappointed to find out that some simple features, for example, pivot
 tables were missing and this forced me back to MS Office.
 
 When do we expect to have these functionalities built in?
Calling Pivot Tables a *simple* feature is the biggest
understatement I have read since years.  :-)

Besides that - a hint for all interested readers (as this is a multi
post): Niklas Nebel has answered the question on the discuss mailing
list. Please follow up there for any further discussions.

Ciao,
Mathias

-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to [EMAIL PROTECTED].
I use it for the OOo lists and only rarely read other mails sent to it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[native-lang] Re: [dev] Re: [users] Re: [discuss] RE: [ooo-announce] OpenOffice.org 2.1 Is Here

2006-12-13 Thread Christian Lohmaier
On Wed, Dec 13, 2006 at 06:08:46PM +0800, [EMAIL PROTECTED] wrote:
 Mathias Bauer wrote:
 [..]
 Besides that - a hint for all interested readers (as this is a multi
 post): Niklas Nebel has answered the question on the discuss mailing
 list. Please follow up there for any further discussions.
 
 
 how to access Niklas Nebel answer on pivot table?

Use the archives...
http://www.mail-archive.com/discuss@openoffice.org/msg12595.html
http://www.openoffice.org/servlets/ReadMsg?list=discussmsgNo=58982

ciao
Christian
-- 
NP: Silverchair - Satin Sheets

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[native-lang] Proposal: Kurdish NLC project

2006-12-13 Thread Erdal Ronahi

Hi,

I am the team leader of a group that translates and promotes free and
open source software in the Kurdish language. We are involved in
OpenOffice.org, Mozilla, GNOME, KDE and Ubuntu localization and
promotion. We also developed the Kurdish MySpell dictionary for
OpenOffice.org.

We just had a lot of success in the Kurdish community and the Kurdish
press with a presentation of the Kurdish translation of Ubuntu. As the
release of OpenOffice.org 2.1 (and it's Kurdish localization for the
first time) is imminent we want to make a step forward and become
official members of the Native Language Confederation.

We find it important to become official members of the NLC, because be
feel that will help us to promote a wider use of the new Kurdish
OpenOffice.org as well as it will be a good starting point to enlarge
the Kurdish OpenOffice.org community independently from the Linux
community.

Localization of OpenOffice.org is continuing.

Best regards,
Erdal Ronahi

Links:
http://pckurd.net Kurdish Free Software Group
http://ubuntu-ku.org Kurdish Ubuntu
http://www.ferheng.org/?Kontrola_rastniv%C3%AEsa_kurd%C3%AE:Deutsch:OpenOffice.org_2_%26amp%3B_MySpell_a_kurd%C3%AE
Provisory Kurdish OpenOffice.org homepage I
http://wiki.ferheng.org/doku.php/wergerandin:openoffice.org Wiki page
for the translation group

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [native-lang] Status update season!

2006-12-13 Thread Clytie Siddall


On 13/12/2006, at 2:26 AM, Charles-H.Schulz 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!


VI: we would have released yesterday but...

we didn't know that the entire QA process had to be completed for all  
builds in order to release.


In fact, had I not stumbled onto the QA list to ask questions about  
an issue, some weeks back, we wouldn't have even known there _was_ a  
separate QA project.


QA is, of course, an integral part of any i18n project. It is  
essential to make sure the translation is checked, reviewed, builds,  
installs and runs in production.


So our release schedule allowed for all that, and we completed it  
ourselves. We translated, reviewed, checked, submitted, then tested  
our builds in production. We were all set to release our language  
yesterday.


Since I've volunteered for the QA project, I've been trying to  
understand the QA tools. I haven't got anywhere with testtool yet,  
but I've been using TCM, and have got part-way through TCM for Mac  
Intel.


However, nobody else in my team has enough time and English combined  
to work out how to use these tools. My original plan was to work them  
out myself, between this release and the next, then write a Howto in  
our language. I've also talked with the other QA people about  
translating the TCM interface into Vietnamese.


We (VI) had absolutely no idea that all these formalized QA  
procedures had to be completed in order to release our translation.


I had actually begun worrying about release procedures, since on any  
other project, I would have seen posts leading up to release,  
reminding i18n volunteers of the deadlines and other tasks to be  
completed in that time. Nothing was said.


I kept re-reading the release schedule, instructions for committing  
translations etc. but couldn't find anything else we had to do. I  
even asked on the QA list exactly where QA fit in with release. I  
finally got an answer the day before release. The formalized QA  
procedures are a prerequisite for release.


I am deeply concerned about the lack of overall information provided  
to people entering the OOo project. This is the only project with  
which I'm involved, where someone entering the project, posting for  
the first time on a mailing list and saying Here I am, and this is  
what I hope to do, or Here I am, what should I do? _doesn't_ get a  
response of this kind:


Welcome X!
Our aims are Y [link to details].
Z [link] is our homepage.
Please read the Howtos and other background information here. [link(s)]
In order to participate, you need to do A, B, C ...


I write this sort of mail myself several times a week on different  
projects' lists.


But in OpenOffice.org, you are just left blundering around in the  
dark. There are occasional pointers, like Rafaella's blessed post  
about the release schedule (one group of facts to which I have clung  
throughout these confused months), but in general, it seems that  
people _assume_ you know all the things you need to know.


Each time I trip over yet another thing I was supposed to know, and  
didn't, because I was never told or pointed to it, I feel even more  
confused.


And if I'm blundering around in the dark, how does this affect my  
team? They have trusted me to get them to release, after years of  
failure and public disgrace.


We worked out a release schedule, took into account everything we  
knew and everything I could find out by asking a lot of questions,  
but in the end, I didn't ask the right questions. I've tripped over  
one too many things in the dark, and I've taken my team with me.


This looks really bad from our community POV. The release which was  
scheduled for yesterday, and for which we were completely ready,  
hasn't occurred. All I can say to my team and other stakeholders is,  
I didn't know about this major prerequisite everyone else knows  
about. I've let them down so badly.


This was supposed to be our first release. We had a whole promotion  
campaign waiting in Vietnam, focussed on releasing yesterday. The  
Department of Science and Technology in Vietnam, several different  
universities in Vietnam, Intel and their business and training  
network throughout Asia, NGOs like Oxfam and AUF, the user network  
(VietLUG, Hanoi LUG etc.) are all set up and waiting to promote the  
use of OpenOffice.org throughout Vietnam. We have grants to stamp CDs.


And it all falls apart, because I didn't know what I was supposed to do.

So our status is just derailed and discouraged.

We don't know what to do from here. All those organizations and  
people expecting the release, and we can't release. I'm the only one  
who understands any of the QA tools, and I understand very little as  
yet. I use a Mac. Most of our users are on Windows and Linux. We've  
done a lot of production testing, but we haven't done the 

Re: [native-lang] Proposal: Kurdish NLC project

2006-12-13 Thread Clytie Siddall


On 14/12/2006, at 11:32 AM, Erdal Ronahi wrote:


I am the team leader of a group that translates and promotes free and
open source software in the Kurdish language. We are involved in
OpenOffice.org, Mozilla, GNOME, KDE and Ubuntu localization and
promotion. We also developed the Kurdish MySpell dictionary for
OpenOffice.org.

snip

As always, it's great to work in the same project with you, Erdal. :)

There's been tremendous progress with Kurdish in the past couple of  
years, and you've been behind every step of it.


Congratulations, and good luck for the future. :)

Based on what I know of Erdal's work in other free-software projects  
like GNOME, KDE and Debian, and on his consistent and impressive  
level of personal effort, I strongly support the inclusion of  
Kurdish, led by Erdal, in the NLC.


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