L10N and I18N Installation Test Day Tomorrow

[Ani Peter]

Hello everyone!

Please note that tomorrow (2012-04-05) we are hosting a Localization and 
Internationalization Installation Test Day [1] to have a look on the 
translations quality for Anaconda and i18n support during installation 
as well as some post install verification tests.

Kindly request all Fedora translators to participate in this test event. 
Please check [1] for details and also feel free to edit the wiki with 
your results.

Thanking you
Best regards
Ani

[1] - 
https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installation

[Ani Peter]

Thank you all for the participation. Please let us know your valuable 
suggestions or feedbacks to make our test events better and have more 
participation.

Best regards
Ani

Ani Peter wrote:
>  Hello everyone!
>
>  Please note that tomorrow (2012-04-05) we are hosting a Localization 
>  and Internationalization Installation Test Day [1] to have a look on 
>  the translations quality for Anaconda and i18n support during 
>  installation as well as some post install verification tests.
>
>  Kindly request all Fedora translators to participate in this test 
>  event. Please check [1] for details and also feel free to edit the 
>  wiki with your results.
>
>  Thanking you
>  Best regards
>  Ani
>
>  [1] - 
>  https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installation
>
>  -- 
>  i18n mailing list
>  i18n(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/i18n

[Christopher Meng]

i will take a look at this,thanks for your reminder.

On Tuesday, April 10, 2012, Ani Peter wrote:

>  Thank you all for the participation. Please let us know your
> valuable
>  suggestions or feedbacks to make our test events better and have more
>  participation.
>
>  Best regards
>  Ani
>
>  Ani Peter wrote:
>
> > Hello everyone!
> >
> > Please note that tomorrow (2012-04-05) we are hosting a Localization and
> > Internationalization Installation Test Day [1] to have a look on the
> > translations quality for Anaconda and i18n support during installation as
> > well as some post install verification tests.
> >
> > Kindly request all Fedora translators to participate in this test event.
> > Please check [1] for details and also feel free to edit the wiki with your
> > results.
> >
> > Thanking you
> > Best regards
> > Ani
> >
> > [1] - https://fedoraproject.org/**wiki/Test_Day:2012-04-05_L10n_**
> >
> I18n_Installation<https://fedoraproject.org/wiki/Test_Day:2012-04-05_L...
> >
> > --
> > i18n mailing list
> > i18n(a)lists.fedoraproject.org
> >
> https://admin.fedoraproject.**org/mailman/listinfo/i18n<https://admin....
> >
>
>  --
>  trans mailing list
>  trans(a)lists.fedoraproject.org
>
> https://admin.fedoraproject.**org/mailman/listinfo/trans<https://admin...


-- 
Sent from Gmail Mobile

[Roman Spirgi]

Hi Ani

I would appreciate to get a reminder a few days before the test day. As
I remember we had a translation test week for F16, which was even better
... So more people get the chance to test.

Cheers,
Roman

Am 10.04.2012 07:47, schrieb Ani Peter:
>  Thank you all for the participation. Please let us know your
> valuable
>  suggestions or feedbacks to make our test events better and have more
>  participation.
>
>  Best regards
>  Ani
>
>  Ani Peter wrote:
> > Hello everyone!
> >
> > Please note that tomorrow (2012-04-05) we are hosting a Localization
> > and Internationalization Installation Test Day [1] to have a look on
> > the translations quality for Anaconda and i18n support during
> > installation as well as some post install verification tests.
> >
> > Kindly request all Fedora translators to participate in this test
> > event. Please check [1] for details and also feel free to edit the
> > wiki with your results.
> >
> > Thanking you
> > Best regards
> > Ani
> >
> > [1] -
> > https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installation
> >
> > -- 
> > i18n mailing list
> > i18n(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/i18n
>
>  -- 
>  trans mailing list
>  trans(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/trans

[Ani Peter]

Hi Roman,

I understand your point and is a very valid suggestion and we are 
looking into it. Will surely take care for F18.

Best regards
Ani

Roman Spirgi wrote:
>  Hi Ani
>
>  I would appreciate to get a reminder a few days before the test day. As
>  I remember we had a translation test week for F16, which was even better
>  ... So more people get the chance to test.
>
>  Cheers,
>  Roman
>
>  Am 10.04.2012 07:47, schrieb Ani Peter:
>    
> > Thank you all for the participation. Please let us know your valuable
> > suggestions or feedbacks to make our test events better and have more
> > participation.
> >
> > Best regards
> > Ani
> >
> > Ani Peter wrote:
> >     
> >> Hello everyone!
> >>
> >> Please note that tomorrow (2012-04-05) we are hosting a Localization
> >> and Internationalization Installation Test Day [1] to have a look on
> >> the translations quality for Anaconda and i18n support during
> >> installation as well as some post install verification tests.
> >>
> >> Kindly request all Fedora translators to participate in this test
> >> event. Please check [1] for details and also feel free to edit the
> >> wiki with your results.
> >>
> >> Thanking you
> >> Best regards
> >> Ani
> >>
> >> [1] -
> >> https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installation
> >>
> >> -- 
> >> i18n mailing list
> >> i18n(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/i18n
> >>       
> > -- 
> > trans mailing list
> > trans(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/trans
> >

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Richard E. van der Luit]

Hi all,

After checking translation for anaconda and discovering translation
errors in some strings the following question raised:

Correcting the faulty string in:

a. f17-branch
b. f16-branch
c. f15-branch
d. Master
e. All above

is necessary to get the corrected translation for the same string *in
all currently* supported releases.

I really don't know.

Who does?

regards

Richard
Dutch TT

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Ani Peter]

Hi Richard,

If I understand your question correctly, I guess you want to make few 
changes to some strings in anaconda and wants to know whether to correct 
these strings in master only or all branches, right? If so, its good to 
make the changes to all branches and master.

Please feel free to ask again if this is not answering your question.

Best regards
Ani


Richard E. van der Luit wrote:
>  Hi all,
>
>  After checking translation for anaconda and discovering translation
>  errors in some strings the following question raised:
>
>  Correcting the faulty string in:
>
>  a. f17-branch
>  b. f16-branch
>  c. f15-branch
>  d. Master
>  e. All above
>
>  is necessary to get the corrected translation for the same string *in
>  all currently* supported releases.
>
>  I really don't know.
>
>  Who does?
>
>  regards
>
>  Richard
>  Dutch TT
>
>
>
>

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Richard E. van der Luit]

Op 17-04-12 06:39, Ani Peter schreef:
>  Hi Richard,
>  
>  If I understand your question correctly, I guess you want to make few
>  changes to some strings in anaconda and wants to know whether to correct
>  these strings in master only or all branches, right? If so, its good to
>  make the changes to all branches and master. 

Yep, so the correct answer is "e. All above"

mmm, not pleased by that, it is very inefficient to have to correct the
same string in 4 sources, especially if you change a term, which implies
correcting many strings.
I know, you can use 'history' in Lotte for this. Still, it's a pain.

Thank you for the response,
regards
Richard


>  
>  Please feel free to ask again if this is not answering your question.
>  
>  Best regards
>  Ani
>  
>  
>  Richard E. van der Luit wrote:
> > Hi all,
> >
> > After checking translation for anaconda and discovering translation
> > errors in some strings the following question raised:
> >
> > Correcting the faulty string in:
> >
> > a. f17-branch
> > b. f16-branch
> > c. f15-branch
> > d. Master
> > e. All above
> >
> > is necessary to get the corrected translation for the same string *in
> > all currently* supported releases.
> >
> > I really don't know.
> >
> > Who does?
> >
> > regards
> >
> > Richard
> > Dutch TT
> >
> >
> >
> >   
>

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Ankit Patel]

On 04/17/2012 02:27 PM, Richard E. van der Luit wrote:
>  Op 17-04-12 06:39, Ani Peter schreef:
> > Hi Richard,
> >
> > If I understand your question correctly, I guess you want to make few
> > changes to some strings in anaconda and wants to know whether to correct
> > these strings in master only or all branches, right? If so, its good to
> > make the changes to all branches and master.
>
>
>  Yep, so the correct answer is "e. All above"
>
>  mmm, not pleased by that, it is very inefficient to have to correct the
>  same string in 4 sources, especially if you change a term, which implies
>  correcting many strings.
>  I know, you can use 'history' in Lotte for this. Still, it's a pain.
>
>  Thank you for the response,
>  regards
>  Richard 
This is indeed an important feature to have for translators, as we don't
care about repositories or branches or so... We just want to update
translations at single place and want it to be applied across.

+1

-- 
Regards,
Ankit Patel
http://www.ankit644.com/

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Yuri Chornoivan]

Tue, 17 Apr 2012 12:37:12 +0300 було написано Ankitkumar Rameshchandra  
Patel <ankit(a)redhat.com&gt;:

>  On 04/17/2012 02:27 PM, Richard E. van der Luit wrote:
> > Op 17-04-12 06:39, Ani Peter schreef:
> >> Hi Richard,
> >>
> >> If I understand your question correctly, I guess you want to make few
> >> changes to some strings in anaconda and wants to know whether to  
> >> correct
> >> these strings in master only or all branches, right? If so, its good to
> >> make the changes to all branches and master.
> >
> >
> > Yep, so the correct answer is "e. All above"
> >
> > mmm, not pleased by that, it is very inefficient to have to correct the
> > same string in 4 sources, especially if you change a term, which implies
> > correcting many strings.
> > I know, you can use 'history' in Lotte for this. Still, it's a pain.
> >
> > Thank you for the response,
> > regards
> > Richard
>
>  This is indeed an important feature to have for translators, as we don't
>  care about repositories or branches or so... We just want to update
>  translations at single place and want it to be applied across.
>
>  +1 
To be honest, I do not see the major problem here.

1. Download PO.
2. Fix it or if it's already fixed do nothing.
3. Upload fixed PO to every branch.
4. Fixed translations will overwrite the old ones.

It's just two minutes of time.

// Alternative way: adopt Weblate ( http://weblate.org/ ). ;)

Best regards,
Yuri

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Kévin Raymond]

>  To be honest, I do not see the major problem here.
>
>  1. Download PO.
>  2. Fix it or if it's already fixed do nothing.
>  3. Upload fixed PO to every branch. 
No, because the PO should be different between branches. If not, they
would only have master…
But it could be the same between branches, you need to ask the
maintainer or check by yourself.

>  4. Fixed translations will overwrite the old ones.
>
>  It's just two minutes of time. 
Depends of 3.


>  // Alternative way: adopt Weblate ( http://weblate.org/ ). ;) 
There are other alternatives:

- download all localy with the transifex client, then tx push -t will
do it for you.
Gitorious is dead actually (500) but you'll be able to use my script
to download all projects :
http://gitorious.org/tiny-scripts/transifex/commits


An other thing to know is that the maintainer could set an option to
share the translation history between projects and or resources under
transifex.net.
It is disabled by default, and you can't see if it's enabled or not if
your'not a maintainer.
I plan to do a mass request to enable this soon :).


-- 
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Yuri Chornoivan]

Tue, 17 Apr 2012 12:53:12 +0300 було написано Kévin Raymond  
<shaiton(a)fedoraproject.org&gt;:

> >
> > To be honest, I do not see the major problem here.
> >
> > 1. Download PO.
> > 2. Fix it or if it's already fixed do nothing.
> > 3. Upload fixed PO to every branch.
>  No, because the PO should be different between branches. If not, they
>  would only have master…
>  But it could be the same between branches, you need to ask the
>  maintainer or check by yourself. 
Strange. Works every time here. ;)

Even with different templates, the system merges only the entries with the  
same msgid strings (it's polib feature, imho).

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Kévin Raymond]

On Tue, Apr 17, 2012 at 12:03 PM, Yuri Chornoivan <yurchor(a)ukr.net&gt; wrote:
>  Tue, 17 Apr 2012 12:53:12 +0300 було написано Kévin Raymond
>  <shaiton(a)fedoraproject.org&gt;:
>
>
> >>
> >> To be honest, I do not see the major problem here.
> >>
> >> 1. Download PO.
> >> 2. Fix it or if it's already fixed do nothing.
> >> 3. Upload fixed PO to every branch.
> >
> > No, because the PO should be different between branches. If not, they
> > would only have master…
> > But it could be the same between branches, you need to ask the
> > maintainer or check by yourself.
>
>
>  Strange. Works every time here. ;)
>
>  Even with different templates, the system merges only the entries with the
>  same msgid strings (it's polib feature, imho). 
Yep sure. Moreover it is stored string by string in TXN, and not file by file.
But using Lotte, it is only matter of few online edit to correct typo



-- 
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Richard E. van der Luit]

Op 17-04-12 12:03, Yuri Chornoivan schreef:
>  Tue, 17 Apr 2012 12:53:12 +0300 було написано Kévin Raymond
>  <shaiton(a)fedoraproject.org&gt;:
>
> >>
> >> To be honest, I do not see the major problem here.
> >>
> >> 1. Download PO.
> >> 2. Fix it or if it's already fixed do nothing.
> >> 3. Upload fixed PO to every branch.
> > No, because the PO should be different between branches. If not, they
> > would only have master…
> > But it could be the same between branches, you need to ask the
> > maintainer or check by yourself.
>
>  Strange. Works every time here. ;)
>
>  Even with different templates, the system merges only the entries with
>  the same msgid strings (it's polib feature, imho). 

Won't work if you want to replace a translation of a term for
consistency with translations of that term in other programs or
documents of the Project, as i regularly have to do.

- how do you know that all strings in all branches are reached by
uploading one just one .po? --> manual check on all sources -> 2 minutes
won't do it.
- which .po is clever to use? The one with the most strings? The most
appearances? --> manual check --> pffff
- are there still strings left to be corrected in the other sources? -->
manual check --> *sigh*, no 'search and replace' feature...

Better open all sources and take Lottes history to check every line,
wereof deed.

What i was looking for, actually, was that one source which has *all*
the strings in it, and let the system sort it out. How 'master' is
master anyway?

regards
Richard

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Yuri Chornoivan]

написане Tue, 17 Apr 2012 17:12:29 +0300, Richard E. van der Luit  
<nippur(a)fedoraproject.org&gt;:

>  Op 17-04-12 12:03, Yuri Chornoivan schreef:
> > Tue, 17 Apr 2012 12:53:12 +0300 було написано Kévin Raymond
> > <shaiton(a)fedoraproject.org&gt;:
> >
> >>>
> >>> To be honest, I do not see the major problem here.
> >>>
> >>> 1. Download PO.
> >>> 2. Fix it or if it's already fixed do nothing.
> >>> 3. Upload fixed PO to every branch.
> >> No, because the PO should be different between branches. If not, they
> >> would only have master…
> >> But it could be the same between branches, you need to ask the
> >> maintainer or check by yourself.
> >
> > Strange. Works every time here. ;)
> >
> > Even with different templates, the system merges only the entries with
> > the same msgid strings (it's polib feature, imho).
>
>
>  Won't work if you want to replace a translation of a term for
>  consistency with translations of that term in other programs or
>  documents of the Project, as i regularly have to do.
>
>  - how do you know that all strings in all branches are reached by
>  uploading one just one .po? --> manual check on all sources -> 2 minutes
>  won't do it. 
If you want to work directly with git repo, I have bad news for you.  
General Transifex workflow does not imply PO (or POT) files in repos at  
all.

You reach exactly the branch that can be derived from the name of the  
catalog branch in Transifex.

About manual check of sources. Once again Lotte is not reliable, it hides  
the translation from translator as good as it can. The results can be very  
unpredictable if string has some formatting in it. If you want to change  
something globally use tx client and some consistency checking instrument,  
i.e. Pology [1]. Then upload all at once with tx client (as it was  
mentioned earlier by Kévin Raymond).

>  - which .po is clever to use? The one with the most strings? The
> most
>  appearances? --> manual check --> pffff 
We have not very wide field: 16/17 branch and current master (believe me  
that the difference between them is negligible). The rest of translations  
cannot be reached for us as source repositories should not contain POs now  
(see above).

On the other hand, translations on Zanata have all necessary equipment to  
change them in the branch needed from (and only from) web-interface.

>  - are there still strings left to be corrected in the other sources?
> -->
>  manual check --> *sigh*, no 'search and replace' feature... 
Use search in /usr/share/locale/<locale>/LC_MESSAGES for installed UI  
translations (docs should be treated by tx client method explained by  
Kévin Raymond). On the other hand, if you do not know if there a mistake  
somewhere, how would you know that there is a mistake at all? ;)

>  Better open all sources and take Lottes history to check every line,
>  wereof deed. 
I hope you are joking.

>  What i was looking for, actually, was that one source which has
> *all*
>  the strings in it, and let the system sort it out. How 'master' is
>  master anyway? 
If you are looking for Fedora only translations, it's tx client snapshot  
of the project or web-only Fedora Zanata instance. We cannot reach  
translations that are not there in a usual way (without bug reporting).  
You can fix the files locally (grep or pology sieve can help you to find  
the necessary files), then sort by day and upload them. But for the fixed  
translations reach the users you have to file bugs against all the  
versions of packages affected.

>  regards
>  Richard 
regards,
Yuri

[1] http://pology.nedohodnik.net/

L10N and I18N Installation Test Day, processing changes in anaconda language files

[Noriko Mizumoto]

I believe 'd. Master' only, see inline.

(2012年04月17日 07:33), Richard E. van der Luit wrote:
>  Hi all,
>  
>  After checking translation for anaconda and discovering translation
>  errors in some strings the following question raised:
>  
>  Correcting the faulty string in:
>  
>  a. f17-branch
>  b. f16-branch
>  c. f15-branch
>  d. Master
>  e. All above
>  
>  is necessary to get the corrected translation for the same string *in
>  all currently* supported releases. 
I understand that Fedora releases are not supported by any particular
organization. No release gets updated version like F17U1.0. It moves
forward next version. There is no point to update translation for older
versions for current system.

Thus I believe 'd. Master' only. Any correction made now will reflect to
f18 and later. But you can try to update 'a f17-branch' as well. Only if
anaconda maintainers decide to update latest translation and pull files
including your updated file, it may be included.

noriko

>  
>  I really don't know.
>  
>  Who does?
>  
>  regards
>  
>  Richard
>  Dutch TT
>  
>  
>  
>  --
>  i18n mailing list
>  i18n(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/i18n

[Noriko Mizumoto]

Hi test group and i18n team

I have already chatted below findings with Ani and Jens on each irc
chnannel, but I thought it would be good to share in the MLs as well. So
here we go.

Two findings.
One: As I joined the test late, I encountered particular problem.
The iso images pointed in the page has been removed sometime btw 14-15
Apr, so the link did not work. For RC3 images, I found that instead diso
images have been placed in different directory. I did not know how to
deal with diso format, but can not complain since RC3 images are not
only for this test purpose. Plus assuming future RC3 images will be
stored as diso format, I like to suggest that a request of composing an
iso image for I18N test can be made as well just like for L10N QA test.
Well, it adds extra task for test group ;p

Two: Testcase Arabic/Asian/Cyrillic/Non-English European Language
Install pages contain unclear instruction. There is no language
selection step to take in f17.  Testcase firstboot page explains about
the command 'firstboot --reconfig', which actually is not working.
Firstboot gives only one chance for test, auto-run after install. It is
highly appreciated to update those information.

Thanks in advance
noriko

(2012年04月11日 19:16), Ani Peter wrote:
>  Hi Roman,
>  
>  I understand your point and is a very valid suggestion and we are
>  looking into it. Will surely take care for F18.
>  
>  Best regards
>  Ani
>  
>  Roman Spirgi wrote:
> > Hi Ani
> >
> > I would appreciate to get a reminder a few days before the test day. As
> > I remember we had a translation test week for F16, which was even better
> > ... So more people get the chance to test.
> >
> > Cheers,
> > Roman
> >
> > Am 10.04.2012 07:47, schrieb Ani Peter:
> >  
> >> Thank you all for the participation. Please let us know your valuable
> >> suggestions or feedbacks to make our test events better and have more
> >> participation.
> >>
> >> Best regards
> >> Ani
> >>
> >> Ani Peter wrote:
> >>    
> >>> Hello everyone!
> >>>
> >>> Please note that tomorrow (2012-04-05) we are hosting a Localization
> >>> and Internationalization Installation Test Day [1] to have a look on
> >>> the translations quality for Anaconda and i18n support during
> >>> installation as well as some post install verification tests.
> >>>
> >>> Kindly request all Fedora translators to participate in this test
> >>> event. Please check [1] for details and also feel free to edit the
> >>> wiki with your results.
> >>>
> >>> Thanking you
> >>> Best regards
> >>> Ani
> >>>
> >>> [1] -
> >>> https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installation
> >>>
> >>>
> >>> -- 
> >>> i18n mailing list
> >>> i18n(a)lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/i18n
> >>>       
> >> -- 
> >> trans mailing list
> >> trans(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/trans
> >>     
>  
>  -- 
>  i18n mailing list
>  i18n(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/i18n

[Alam]

04/20/2012 09:38 AM ਨੂੰ, Noriko Mizumoto ਨੇ ਲਿਖਿਆ:
>  Hi test group and i18n team
>
>  I have already chatted below findings with Ani and Jens on each irc
>  chnannel, but I thought it would be good to share in the MLs as well. So
>  here we go.
>
>  Two findings.
>  One: As I joined the test late, I encountered particular problem.
>  The iso images pointed in the page has been removed sometime btw 14-15
>  Apr, so the link did not work. For RC3 images, I found that instead diso
>  images have been placed in different directory. I did not know how to
>  deal with diso format, but can not complain since RC3 images are not
>  only for this test purpose. Plus assuming future RC3 images will be
>  stored as diso format, I like to suggest that a request of composing an
>  iso image for I18N test can be made as well just like for L10N QA test.
>  Well, it adds extra task for test group ;p 
RC3 was stage iso (so removed), which
used as that is only latest iso 
available at 4-5 Apr to test. latest Stage image for RC4.1 (now released 
beta) was available on 11Apr. But as you suggested (and did for l10n 
test day) creation of specially ISO for all test day is task from next 
Fedora testing.
>  Two: Testcase Arabic/Asian/Cyrillic/Non-English European Language
>  Install pages contain unclear instruction. There is no language
>  selection step to take in f17.  Testcase firstboot page explains about
>  the command 'firstboot --reconfig', which actually is not working.
>  Firstboot gives only one chance for test, auto-run after install. It is
>  highly appreciated to update those information. 
During installation it was observed
and will update for next testing phase.

thanks for feedback.

A S Alam

[Noriko Mizumoto]

>  Kindly request all Fedora translators to participate in this test
> event.
>  Please check [1] for details and also feel free to edit the wiki with
>  your results. 
Hi I18N team

Sorry coming late, some more language translators made their time and
performed the test this week. Please re-visit the result page for update
[1]. We hope that the bugs and the comments to be addressed.
Let us know if further we can help for improving the quality.

[1]:https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installat...

noriko