incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kazunari Hirano <khir...@gmail.com>
Subject Re: Native Language vs l10n
Date Sat, 18 Jun 2011 20:50:12 GMT
Hi Dennis and all,

I would like to answer Dennis' questions :)

On Sat, Jun 18, 2011 at 5:30 AM, Dennis E. Hamilton
<dennis.hamilton@acm.org> wrote:
> On ooo-dev we are talking now about how to support language communities.

Thanks!

> Please help my understanding.  I am ignorant.  I have too many questions.  Answer in
parts may be good.

I am happy to answer your questions.

> Does the Japanese Language Project do any work to prepare distributions for the Japanese
Language community?  Could it do so?

Yes, we do, and Yes, we could if we have enough resources to do it.
As you may know, "distributions" doesn't mean just building
OpenOffice.org installsets and langpacks and uploading them to the
server.
and say "Use it!" :)

I am proud of ja members maintaining this page :)

http://wiki.services.openoffice.org/wiki/Product_Release/builds_uploaded

The most recent entry is 13-Apr-2011,   OOo 3.4 beta, OOO340_m0, as you see.
The most recent stable version 3.3.0 was released on 27-Jan-2011.
Now can you find when 3.3.0 beta1 was released?
It was on 10-Aug-2010, OOo-Dev 3.3.0 beta1, OOO330_m3, as you see.
Between the 3.3.0 beta1 (27-Jan-2011) and the 3.3.0 release
(10-Aug-2010), how many RCs do you count?
RC is Release Candidate :)  Did you count RC10? Good.  You are correct :)
RC10!  During RC time we did QA (Quality Assurance) tests.
http://wiki.services.openoffice.org/wiki/JA/QA/Release/3.3.0#.E6.8B.85.E5.BD.93.E8.80.85
We made clear when who does and did what (excerpt):
1. Ja QA manager appointed, 2009/8/3
2. 3.3.0 QA wiki page created, 2010/10/19
3. 3.3.0 QA forum set up, 2010/10/19
4. Release stopper issue noticed, 2010/10/18
5. Release candidate builds noticed, 2010/10/20, 10/26
6. Submit builds to QATrack, 2010/10/23
7. Call for QA testers (volunteers), 2010/10/27
8. QA IRC meeting
9. QA test started
10, QA test results reported, 2011/1/30
11. Distribution request issue filed, 2011/1/30
12. Announce the end of QA test at the forum
13. Announce the end of QA test to the ja announce list
14. 3.3.0 release announcement draft, 2011/1/30
15. Translate 3.3.0 English PR and announce it, 2011/2/1
16. Update the Ja download page, 2011/2/2 http://ja.openoffice.org/download/
17. Update the Ja top page, 2011/2/2 http://ja.openoffice.org/
18. Confirm the download page and the top page work well, 2011/2/2
19. Annouce 3.3.0 ja release at announce@ja.openoffice.org, 2011/2/2
http://wiki.services.openoffice.org/wiki/PressReleases
20. Confirm the ja update page at http://update.services.openoffice.org/ooo/
21. Add the 3.3.0 QA to Ja QA history on http://ja.openoffice.org/qa/

We used many tools such as Issue Tracker, Mailing lists, Forum,
QATrack, QUASTe, WIKI, TCM to have QA works done and release quality
OpenOffice.org 3.3.0 Japanese builds, installsets and langpacks.
If you want to learn about  tools above, go to http://qa.openoffice.org/
And 3.3.0 ja QA test matrix here.
http://wiki.services.openoffice.org/wiki/JA/QA/Release/3.3.0/Issues#.E3.83.AA.E3.83.AA.E3.83.BC.E3.82.B9.E5.93.81.E8.B3.AA.E4.BF.9D.E8.A8.BC.E3.83.9E.E3.83.88.E3.83.AA.E3.83.83.E3.82.AF.E3.82.B9
We were lucky when we did 3.3.0 QA because we had many testers
(volunteers) and we had a vigorous QA manager.
:)
The Japanese Language Project can do some work to prepare
distributions for the Japanese Language community if we have tools on
a stable infrastructure and we are lucky enough to get resources
(volunteers).

> Does it provide the translation work for the distribution?

Yes, we do.
http://wiki.services.openoffice.org/wiki/JA/translation/3.3
We provided the translation for OpenOffice.org 3.3.0
We couldn't provide the translation for OpenOffice.org 3.4.0 because
we had no resource.

> Is all of the release internationalization done in the language pack?
If you mean localization of User Interface and Online Help, yes they
are in the language pack.
We translate them into our native language on Pootle.
http://wiki.services.openoffice.org/wiki/Pootle_User_Guide

> I see http://ja.openoffice.org
> http://ja.openoffice.org/howtoparticipate.html
> I see openoffice.org SVN subtree for the JA language project.
> I see ja project issues in the combined Bugzilla issue tracker.
> The SVN and Bugzilla infrastructure seems to be in English.
> Could this work separately?

Sorry but I don't see what "this work" is.  Which work? :)

> I also see
> http://ftp-srv2.kddilabs.jp/office/openoffice/localized/ja/3.3.0/
> I think this is mirror of
> ftp://ftp.osuosl.org/pub/openoffice/localized/ja/3.3.0/
> Yes?

I think ftp://ftp.osuosl.org/pub/openoffice/localized/ja/3.3.0/ is
also one of mirror sites.
http://distribution.openoffice.org/mirrors/#mirrors
:)

> What is your thinking about parts of Japanese language project working separate from
Apache development?  About coordination of language pack and Apache release and QA?  About
ways to avoid delays in release to users in language communities?

I don't know the separation works :)

If you take a look at the directory in the mirror, you will find the
following builds.
ftp://ftp.osuosl.org/pub/openoffice/localized/ja/3.3.0/
OOo_3.3.0_Linux_x86-64_install-deb_ja.tar.gz
OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_ja.tar.gz
OOo_3.3.0_Linux_x86-64_langpack-rpm_ja.tar.gz
OOo_3.3.0_Linux_x86_install-deb_ja.tar.gz
OOo_3.3.0_Linux_x86_install-rpm-wJRE_ja.tar.gz
OOo_3.3.0_Linux_x86_install-rpm_ja.tar.gz
OOo_3.3.0_Linux_x86_langpack-deb_ja.tar.gz
OOo_3.3.0_Linux_x86_langpack-rpm_ja.tar.gz
OOo_3.3.0_MacOS_PPC_install_ja.dmg
OOo_3.3.0_MacOS_x86_install_ja.dmg
OOo_3.3.0_MacOS_x86_langpack_ja.dmg
OOo_3.3.0_Solaris_Sparc_install-wJRE_ja.tar.gz
OOo_3.3.0_Solaris_Sparc_langpack_ja.tar.gz
OOo_3.3.0_Solaris_x86_install-wJRE_ja.tar.gz
OOo_3.3.0_Solaris_x86_langpack_ja.tar.gz
OOo_3.3.0_Win_x86_install-wJRE_ja.exe
OOo_3.3.0_Win_x86_install_ja.exe
OOo_3.3.0_Win_x86_langpack_ja.exe

We QA-tested them and approved them to be released and uploaded to the server.

You see three kinds of builds for each platform.
_install-wJRE_ja, _install_ja and _langpack_ja.
_langpack_ja is integrated in _install-wJRE_ja and _install_ja.

I think a "language project" as a whole should get involved in Apache
release and QA.

Thanks,
khirano

Mime
View raw message