You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Sebastien Goasguen <ru...@gmail.com> on 2013/04/16 14:25:13 UTC
[DOCS][TRANSLATIONS] Upate
Hi,
There has been some terrific progress on the translations.
The easiest way to share it is to check the Transifex dashboard, below are some screenshots:
The runbook:
http://awesomescreenshot.com/0bd163zldd
The UI:
http://awesomescreenshot.com/089163zva2
The entire docs set:
http://awesomescreenshot.com/01c163zq63
Since 4.1 is not out yet, there is time to finish those last 3% on the UI translations.
Keep getting the word out, forward to friends and let's all make CloudStack a truly worldwide project.
Cheers,
-Sebastien
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 16/04/2013 14:45, Sebastien Goasguen a ecrit :
> On Apr 16, 2013, at 10:40 AM, Gavin Lee<ga...@gmail.com> wrote:
>
>> The UI for 4.1 branch is ok, there is one case relate to the encoding issue:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-870
> This was solved in https://issues.apache.org/jira/browse/CLOUDSTACK-1517
> I see that 870 is closed now.
>
>> Since messages_zh_CN.properties and messages_ja.properties file under resource
>> folder are not human readable, how to translate or modify the content?
>>
>>
> I think milamber is using: http://www.cantamen.com/i18nedit.php to deal with the encoding.
Yes, I18Nedit to convert native encoding (like ISO-8859-1, EUC-JP, etc)
to ASCII with unicode
>
> the files needed to be encoded that way to render properly in the UI.
2 requirements for a good display of Web UI :
* resource file must be in ASCII with unicode (for all chars)
* (only for some language like French, Italian, Spanish, etc.) the quote
' in sentence inside, must have a backslash before \' (dictionary.jsp
contains the key/value dictionary in a javascript code) This points
isn't covering by I18Nedit, but a traditional search/replace in an editor.
Milamber
>
>> On Tue, Apr 16, 2013 at 10:05 PM, Sebastien Goasguen<ru...@gmail.com>wrote:
>>
>>> On Apr 16, 2013, at 9:41 AM, Gavin Lee<ga...@gmail.com> wrote:
>>>
>>>> Yes, Traditional Chinese moving very quickly.
>>>> Hopefully, the other languages can have more contributors.
>>>>
>>>> For the UI part, I saw the characters are not recognizable (browser
>>>> encoding setting: auto detect& Unicode UTF-8):
>>>> ja: http://snag.gy/AVsbU.jpg
>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>> Hum, we fixed some encodings so that it would work in the UI. Have you
>>> tried to build the 4.1 branch and tested the UI itself, rather than
>>> transifex.
>>>
>>> Adding Milamber has he masters encoding for l10n.
>>>
>>> -sebastien
>>>
>>>> The other languages are ok.
>>>>
>>>>
>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<runseb@gmail.com
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> There has been some terrific progress on the translations.
>>>>>
>>>>> The easiest way to share it is to check the Transifex dashboard, below
>>> are
>>>>> some screenshots:
>>>>>
>>>>> The runbook:
>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>
>>>>> The UI:
>>>>> http://awesomescreenshot.com/089163zva2
>>>>>
>>>>> The entire docs set:
>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>
>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on the
>>> UI
>>>>> translations.
>>>>>
>>>>> Keep getting the word out, forward to friends and let's all make
>>>>> CloudStack a truly worldwide project.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> -Sebastien
>>>>
>>>>
>>>>
>>>> --
>>>> Gavin
>>>
>>
>> --
>> Gavin
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Go Chiba <go...@gmail.com>.
Gavin, I running 4.1 repository and all of languages of zh_CN are working
well as below.
http://gyazo.com/6dbc68ecc1ee4b70feec9ff53c51df99
In the previous, ja_JP and zh_CN had a encoding problem as you said, but I
believe
newest 4.1 repository are fixed and you could running it on UTF-8 supported
borwser :)
Go Chiba
On Tue, Apr 16, 2013 at 11:45 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Apr 16, 2013, at 10:40 AM, Gavin Lee <ga...@gmail.com> wrote:
>
> > The UI for 4.1 branch is ok, there is one case relate to the encoding
> issue:
> > https://issues.apache.org/jira/browse/CLOUDSTACK-870
>
> This was solved in https://issues.apache.org/jira/browse/CLOUDSTACK-1517
> I see that 870 is closed now.
>
> >
> > Since messages_zh_CN.properties and messages_ja.properties file under
> resource
> > folder are not human readable, how to translate or modify the content?
> >
> >
>
> I think milamber is using: http://www.cantamen.com/i18nedit.php to deal
> with the encoding.
>
> the files needed to be encoded that way to render properly in the UI.
>
> > On Tue, Apr 16, 2013 at 10:05 PM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
> >
> >>
> >> On Apr 16, 2013, at 9:41 AM, Gavin Lee <ga...@gmail.com> wrote:
> >>
> >>> Yes, Traditional Chinese moving very quickly.
> >>> Hopefully, the other languages can have more contributors.
> >>>
> >>> For the UI part, I saw the characters are not recognizable (browser
> >>> encoding setting: auto detect & Unicode UTF-8):
> >>> ja: http://snag.gy/AVsbU.jpg
> >>> zh_CN: http://snag.gy/MxbBS.jpg
> >>
> >> Hum, we fixed some encodings so that it would work in the UI. Have you
> >> tried to build the 4.1 branch and tested the UI itself, rather than
> >> transifex.
> >>
> >> Adding Milamber has he masters encoding for l10n.
> >>
> >> -sebastien
> >>
> >>>
> >>> The other languages are ok.
> >>>
> >>>
> >>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen <runseb@gmail.com
> >>> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> There has been some terrific progress on the translations.
> >>>>
> >>>> The easiest way to share it is to check the Transifex dashboard, below
> >> are
> >>>> some screenshots:
> >>>>
> >>>> The runbook:
> >>>> http://awesomescreenshot.com/0bd163zldd
> >>>>
> >>>> The UI:
> >>>> http://awesomescreenshot.com/089163zva2
> >>>>
> >>>> The entire docs set:
> >>>> http://awesomescreenshot.com/01c163zq63
> >>>>
> >>>> Since 4.1 is not out yet, there is time to finish those last 3% on the
> >> UI
> >>>> translations.
> >>>>
> >>>> Keep getting the word out, forward to friends and let's all make
> >>>> CloudStack a truly worldwide project.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> -Sebastien
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Gavin
> >>
> >>
> >
> >
> > --
> > Gavin
>
>
--
千葉 豪 Go Chiba
E-mail:go.chiba@gmail.com
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 16, 2013, at 10:40 AM, Gavin Lee <ga...@gmail.com> wrote:
> The UI for 4.1 branch is ok, there is one case relate to the encoding issue:
> https://issues.apache.org/jira/browse/CLOUDSTACK-870
This was solved in https://issues.apache.org/jira/browse/CLOUDSTACK-1517
I see that 870 is closed now.
>
> Since messages_zh_CN.properties and messages_ja.properties file under resource
> folder are not human readable, how to translate or modify the content?
>
>
I think milamber is using: http://www.cantamen.com/i18nedit.php to deal with the encoding.
the files needed to be encoded that way to render properly in the UI.
> On Tue, Apr 16, 2013 at 10:05 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
>>
>> On Apr 16, 2013, at 9:41 AM, Gavin Lee <ga...@gmail.com> wrote:
>>
>>> Yes, Traditional Chinese moving very quickly.
>>> Hopefully, the other languages can have more contributors.
>>>
>>> For the UI part, I saw the characters are not recognizable (browser
>>> encoding setting: auto detect & Unicode UTF-8):
>>> ja: http://snag.gy/AVsbU.jpg
>>> zh_CN: http://snag.gy/MxbBS.jpg
>>
>> Hum, we fixed some encodings so that it would work in the UI. Have you
>> tried to build the 4.1 branch and tested the UI itself, rather than
>> transifex.
>>
>> Adding Milamber has he masters encoding for l10n.
>>
>> -sebastien
>>
>>>
>>> The other languages are ok.
>>>
>>>
>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen <runseb@gmail.com
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> There has been some terrific progress on the translations.
>>>>
>>>> The easiest way to share it is to check the Transifex dashboard, below
>> are
>>>> some screenshots:
>>>>
>>>> The runbook:
>>>> http://awesomescreenshot.com/0bd163zldd
>>>>
>>>> The UI:
>>>> http://awesomescreenshot.com/089163zva2
>>>>
>>>> The entire docs set:
>>>> http://awesomescreenshot.com/01c163zq63
>>>>
>>>> Since 4.1 is not out yet, there is time to finish those last 3% on the
>> UI
>>>> translations.
>>>>
>>>> Keep getting the word out, forward to friends and let's all make
>>>> CloudStack a truly worldwide project.
>>>>
>>>> Cheers,
>>>>
>>>> -Sebastien
>>>
>>>
>>>
>>>
>>> --
>>> Gavin
>>
>>
>
>
> --
> Gavin
Re: [DOCS][TRANSLATIONS] Upate
Posted by Gavin Lee <ga...@gmail.com>.
The UI for 4.1 branch is ok, there is one case relate to the encoding issue:
https://issues.apache.org/jira/browse/CLOUDSTACK-870
Since messages_zh_CN.properties and messages_ja.properties file under resource
folder are not human readable, how to translate or modify the content?
On Tue, Apr 16, 2013 at 10:05 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Apr 16, 2013, at 9:41 AM, Gavin Lee <ga...@gmail.com> wrote:
>
> > Yes, Traditional Chinese moving very quickly.
> > Hopefully, the other languages can have more contributors.
> >
> > For the UI part, I saw the characters are not recognizable (browser
> > encoding setting: auto detect & Unicode UTF-8):
> > ja: http://snag.gy/AVsbU.jpg
> > zh_CN: http://snag.gy/MxbBS.jpg
>
> Hum, we fixed some encodings so that it would work in the UI. Have you
> tried to build the 4.1 branch and tested the UI itself, rather than
> transifex.
>
> Adding Milamber has he masters encoding for l10n.
>
> -sebastien
>
> >
> > The other languages are ok.
> >
> >
> > On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
> >
> >> Hi,
> >>
> >> There has been some terrific progress on the translations.
> >>
> >> The easiest way to share it is to check the Transifex dashboard, below
> are
> >> some screenshots:
> >>
> >> The runbook:
> >> http://awesomescreenshot.com/0bd163zldd
> >>
> >> The UI:
> >> http://awesomescreenshot.com/089163zva2
> >>
> >> The entire docs set:
> >> http://awesomescreenshot.com/01c163zq63
> >>
> >> Since 4.1 is not out yet, there is time to finish those last 3% on the
> UI
> >> translations.
> >>
> >> Keep getting the word out, forward to friends and let's all make
> >> CloudStack a truly worldwide project.
> >>
> >> Cheers,
> >>
> >> -Sebastien
> >
> >
> >
> >
> > --
> > Gavin
>
>
--
Gavin
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 16, 2013, at 9:41 AM, Gavin Lee <ga...@gmail.com> wrote:
> Yes, Traditional Chinese moving very quickly.
> Hopefully, the other languages can have more contributors.
>
> For the UI part, I saw the characters are not recognizable (browser
> encoding setting: auto detect & Unicode UTF-8):
> ja: http://snag.gy/AVsbU.jpg
> zh_CN: http://snag.gy/MxbBS.jpg
Hum, we fixed some encodings so that it would work in the UI. Have you tried to build the 4.1 branch and tested the UI itself, rather than transifex.
Adding Milamber has he masters encoding for l10n.
-sebastien
>
> The other languages are ok.
>
>
> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
>> Hi,
>>
>> There has been some terrific progress on the translations.
>>
>> The easiest way to share it is to check the Transifex dashboard, below are
>> some screenshots:
>>
>> The runbook:
>> http://awesomescreenshot.com/0bd163zldd
>>
>> The UI:
>> http://awesomescreenshot.com/089163zva2
>>
>> The entire docs set:
>> http://awesomescreenshot.com/01c163zq63
>>
>> Since 4.1 is not out yet, there is time to finish those last 3% on the UI
>> translations.
>>
>> Keep getting the word out, forward to friends and let's all make
>> CloudStack a truly worldwide project.
>>
>> Cheers,
>>
>> -Sebastien
>
>
>
>
> --
> Gavin
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 30, 2013, at 5:26 AM, Isaac Chiang <is...@gmail.com> wrote:
> Hi Sebastien:
>
> We're hosting a blog for CloudStack in Taiwan. I've write an article for
> sharing the translation experience with Transifex. Hope it does help :)
>
> http://www.cloudstack-tw.org/2013/04/translation-with-transifex.html
>
> Let me know if I have to fix some wording, I'm really not good at this.
>
Isaac, that's perfect. I just tweeted it
thanks
> Thanks & best regards
>
> Isaac
>
>
> On Mon, Apr 29, 2013 at 4:30 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
>>
>> On Apr 28, 2013, at 8:33 AM, Isaac Chiang <is...@gmail.com> wrote:
>>
>>> Hi all:
>>> The Glossary function on Transifex is quite awesome. I captured
>>> some screenshots for it.
>>>
>>> http://i.imgur.com/WPOcVsI.png
>>>
>>> The link above is the Glossary page on Transifex, we can add new term
>> here.
>>>
>>> We need to determine this term is a noun, verb or something else (There
>> is
>>> a combo box for it ) and corresponding translation. We can also add some
>>> comment of it (Avoid misunderstanding if you're co-working with someone).
>>>
>>> When you are translating on the page(link below), and if you select the
>> the
>>> "Glossary" tab, the glossary tab window will show the added terms
>>> associated to the sentence you are translating as a hint.
>>>
>>> http://i.imgur.com/GqD07pn.png
>>>
>>> The function can avoid inconsistent problem and better started in the
>>> beginning of translation. I am too late for discovering this function. So
>>> the zh_TW's document got lots of inconsistent translation problem. And
>> I'm
>>> now rebuilding the dictionary :(
>>>
>>> For your information and happy translating! :D
>>>
>>
>> Thanks a lot Isaac, it would be great if you could write a blog about this.
>>
>>> Regards
>>>
>>> Isaac
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Apr 24, 2013 at 4:20 PM, Sebastien Goasguen <runseb@gmail.com
>>> wrote:
>>>
>>>>
>>>> On Apr 24, 2013, at 4:18 AM, Isaac Chiang <is...@gmail.com>
>> wrote:
>>>>
>>>>> I Get it :) I'll investigate this function deeper to see how it can
>> help
>>>>> us.
>>>>
>>>> Terrific, I was hoping you would say that :)
>>>>
>>>>>
>>>>> Many thanks.
>>>>>
>>>>> Isaac
>>>>>
>>>>>
>>>>> On Wed, Apr 24, 2013 at 4:11 PM, Sebastien Goasguen <runseb@gmail.com
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> Hi Sebastien:
>>>>>>>
>>>>>>> Thanks!! I see the "View glossary" button just right at the
>>>>>>> upper right corner of the table in this page:
>>>>>>>
>>>>>>> https://www.transifex.com/projects/p/ACS_DOCS/
>>>>>>>
>>>>>>> After entering the glossary page, I am able to select language for
>>>>>> glossary
>>>>>>> and add new term.
>>>>>>>
>>>>>>> So I'm wondering if this glossary table will be appended to the
>>>> document
>>>>>> or
>>>>>>> it just provide the hint
>>>>>>>
>>>>>>> when we're translating?
>>>>>>
>>>>>> We are not using it:
>>>>>>
>>>>>> http://help.transifex.com/features/glossary.html
>>>>>>
>>>>>> However we could to insure consistency of the translations between
>>>>>> translators of the same language.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>>
>>>>>>> Isaac
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <
>> runseb@gmail.com
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi all:
>>>>>>>>> I have a few questions and looking for help. After the documents
>>>>>>>>> have been translated, can I use Transifex to review these
>> documents?
>>>>>>>> Cause
>>>>>>>>> I noticed that some of the terminology aren't consistent during the
>>>>>>>>> translation and the language sources are too large for me to
>> handling
>>>>>> the
>>>>>>>>> review process. So I'm wondering if it is possible for a normal
>> user
>>>> in
>>>>>>>>> Transifex to mark the sentence as reviewed and prevent from
>> reviewing
>>>>>> it
>>>>>>>>> twice?
>>>>>>>>
>>>>>>>> Isaac, considering you translated 95% of the documentation in zh-TW
>> I
>>>>>> made
>>>>>>>> you a maintainer of the ACS_DOCS
>>>>>>>> You should be able to review your own translations, string by
>> string.
>>>>>>>>>
>>>>>>>>> Another question is about the glossary, is it part of translation
>>>>>> program
>>>>>>>>> or a assistant mechanism to support translation?
>>>>>>>>
>>>>>>>> Don't know, I have never looked at the glossary. Where do you see
>> it ?
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks & best regards
>>>>>>>>>
>>>>>>>>> Isaac
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com>
>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Following Milamber's guide , below process I used for
>>>>>>>>>> 4.1.xmessage.properties on zh_CN:
>>>>>>>>>> 1. git pull for the latest messages_zh_CN.properties
>>>>>>>>>> 2. native2ascii -reverse messages_zh_CN.properties
>>>>>>>>>> /tmp/zh_CN.properties.native -encoding utf8
>>>>>>>>>> 3. copy to the CloudStack_UI transifex project:
>>>>>>>>>> cp/tmp/zh_CN.properties.native /
>>>>>>>>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>>>>>>>>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>>>>>>>>>> 5. Do translation on transifex, there are some untranslated items
>>>> when
>>>>>>>>>> syncing with en.properties
>>>>>>>>>> 6. tx pull -a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Then convert to ascii with unicode, the i18nedit tools throws
>>>>>>>> exception, I
>>>>>>>>>> tried native2ascii command as below and UI display correctly:
>>>>>>>>>> native2ascii -encoding UTF-8 zh_CN.properties
>>>>>> messages_zh_CN.properties
>>>>>>>>>>
>>>>>>>>>> Are the whole processes above correct or not?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <
>>>>>> runseb@gmail.com
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Milamber, I made you a manager of the transifex project so you
>> can
>>>>>> help
>>>>>>>>>>> fixing those issues.
>>>>>>>>>>>
>>>>>>>>>>> -sebastien
>>>>>>>>>>>
>>>>>>>>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org>
>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>>>>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org>
>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>>>>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>>>>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> For the UI part, I saw the characters are not recognizable
>>>>>> (browser
>>>>>>>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>>>>>>>>>> This screenshots shows some characters with a incorrect
>> encoding
>>>>>>>> (try
>>>>>>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>>>>>>>> encoding
>>>>>>>>>> is
>>>>>>>>>>> a UTF-8, I think)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> With Sebgoa, we have correct all UI ressource file to have
>> only
>>>>>> one
>>>>>>>>>>> encoding charset in this files (ASCII with unicode). The
>> transifex
>>>>>> data
>>>>>>>>>>> isn't up-to-date.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>>>>>>>>>> resources files (except FR already done) from branch 4.1 to
>>>>>> transifex.
>>>>>>>>>>>>>> The last version of resources files is ASCII with unicode for
>>>> *all
>>>>>>>>>>> chars* in each file, and now transifex keep the unicode char
>> (check
>>>>>>>> with
>>>>>>>>>> FR
>>>>>>>>>>> download for use)
>>>>>>>>>>>>
>>>>>>>>>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>>>>>>>>>
>>>>>>>>>>>>> The way the original workflow was:
>>>>>>>>>>>>> -Upload new versions of the resources file in english
>>>>>>>>>>>>> -Translators create a new language in transifex.
>>>>>>>>>>>>> -Download new language resources file
>>>>>>>>>>>>> -Fix encoding
>>>>>>>>>>>>
>>>>>>>>>>>> For the fix encoding step, we can use this (unix and JDK)
>> commands
>>>>>> for
>>>>>>>>>>> each language:
>>>>>>>>>>>>
>>>>>>>>>>>> CODELANG=it_IT
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>>>>>>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>>>>>>>
>>>>>>>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>>>>>>>>>> native2ascii ${FILE_TRANSIFEX}
>> /tmp/${FILE_RES}.ascii-with-unicode
>>>>>>>>>>>>
>>>>>>>>>>>> # sort key, add a double-backslash before the quote char ( ' ==>
>>>>>> \\' )
>>>>>>>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f |
>> uniq
>>>> |
>>>>>>>> sed
>>>>>>>>>>> "s/'/\\\\\\\\\'/g" >
>>>>>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>>>>>>>>>>
>>>>>>>>>>>> # Define Apache Licence Header (one long line)
>>>>>>>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF)
>>>> under
>>>>>>>>>>> one\n# or more contributor license agreements. See the NOTICE
>>>>>> file\n#
>>>>>>>>>>> distributed with this work for additional information\n#
>> regarding
>>>>>>>>>>> copyright ownership. The ASF licenses this file\n# to you under
>>>> the
>>>>>>>>>> Apache
>>>>>>>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this
>>>> file
>>>>>>>>>> except
>>>>>>>>>>> in compliance\n# with the License. You may obtain a copy of the
>>>>>>>> License
>>>>>>>>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n#Unless
>>>>>>>>>>> required by applicable law or agreed to in writing,\n# software
>>>>>>>>>> distributed
>>>>>>>>>>> under the License is distributed on an\n# \"AS IS\" BASIS,
>> WITHOUT
>>>>>>>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or
>> implied.
>>>>>>>> See
>>>>>>>>>>> the License for the\n# specific language governing permissions
>> and
>>>>>>>>>>> limitations\n# under the License."
>>>>>>>>>>>>
>>>>>>>>>>>> # Re-introduce the AL2 header
>>>>>>>>>>>> echo -e "$AL2_STRING" | cat -
>>>>>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
>>>>>>>>>>> ./FOR_REPO_${FILE_RES}
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> So I never uploaded the language specific resource file to
>>>>>> transifex.
>>>>>>>>>>> Won't we have a problem that they won't stay in sync with the
>> en-US
>>>>>>>>>>> resource file, if it gets changed ?
>>>>>>>>>>>>
>>>>>>>>>>>> On upload, Transifex seems only get the matching key with source
>>>>>>>>>>> language.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> In any case I uploaded the ja-JP resource file and the result
>> on
>>>>>>>>>>> transifex is less than optimal, check the unreviewed strings,
>> there
>>>>>> is
>>>>>>>> a
>>>>>>>>>>> mix of encoding.
>>>>>>>>>>>>
>>>>>>>>>>>> We needs to revert the native to ascii convert.
>>>>>>>>>>>> We can use this steps for each language before uploading on
>>>>>> transifex
>>>>>>>> :
>>>>>>>>>>>>
>>>>>>>>>>>> CODELANG=ja
>>>>>>>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>>>>>>>
>>>>>>>>>>>> # Revert convert
>>>>>>>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>>>>>>>>>
>>>>>>>>>>>> # Remove double backslashes before quote
>>>>>>>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 >
>> ${FILE_RES}.native
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I've tested this commandes for download/upload with French
>>>> language,
>>>>>>>>>> and
>>>>>>>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I can make one shell script to automate this, and put in a tools
>>>> dir
>>>>>>>> in
>>>>>>>>>>> CS git repo.
>>>>>>>>>>>>
>>>>>>>>>>>> Milamber
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Milamber
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The other languages are ok.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>>>>>>>>>> runseb@gmail.com
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The easiest way to share it is to check the Transifex
>>>> dashboard,
>>>>>>>>>>> below are
>>>>>>>>>>>>>>>> some screenshots:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The runbook:
>>>>>>>>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The UI:
>>>>>>>>>>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The entire docs set:
>>>>>>>>>>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last
>>>> 3%
>>>>>> on
>>>>>>>>>>> the UI
>>>>>>>>>>>>>>>> translations.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Keep getting the word out, forward to friends and let's all
>>>> make
>>>>>>>>>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> -Sebastien
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Gavin
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Isaac Chiang <is...@gmail.com>.
Hi Sebastien:
We're hosting a blog for CloudStack in Taiwan. I've write an article for
sharing the translation experience with Transifex. Hope it does help :)
http://www.cloudstack-tw.org/2013/04/translation-with-transifex.html
Let me know if I have to fix some wording, I'm really not good at this.
Thanks & best regards
Isaac
On Mon, Apr 29, 2013 at 4:30 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Apr 28, 2013, at 8:33 AM, Isaac Chiang <is...@gmail.com> wrote:
>
> > Hi all:
> > The Glossary function on Transifex is quite awesome. I captured
> > some screenshots for it.
> >
> > http://i.imgur.com/WPOcVsI.png
> >
> > The link above is the Glossary page on Transifex, we can add new term
> here.
> >
> > We need to determine this term is a noun, verb or something else (There
> is
> > a combo box for it ) and corresponding translation. We can also add some
> > comment of it (Avoid misunderstanding if you're co-working with someone).
> >
> > When you are translating on the page(link below), and if you select the
> the
> > "Glossary" tab, the glossary tab window will show the added terms
> > associated to the sentence you are translating as a hint.
> >
> > http://i.imgur.com/GqD07pn.png
> >
> > The function can avoid inconsistent problem and better started in the
> > beginning of translation. I am too late for discovering this function. So
> > the zh_TW's document got lots of inconsistent translation problem. And
> I'm
> > now rebuilding the dictionary :(
> >
> > For your information and happy translating! :D
> >
>
> Thanks a lot Isaac, it would be great if you could write a blog about this.
>
> > Regards
> >
> > Isaac
> >
> >
> >
> >
> >
> >
> > On Wed, Apr 24, 2013 at 4:20 PM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
> >
> >>
> >> On Apr 24, 2013, at 4:18 AM, Isaac Chiang <is...@gmail.com>
> wrote:
> >>
> >>> I Get it :) I'll investigate this function deeper to see how it can
> help
> >>> us.
> >>
> >> Terrific, I was hoping you would say that :)
> >>
> >>>
> >>> Many thanks.
> >>>
> >>> Isaac
> >>>
> >>>
> >>> On Wed, Apr 24, 2013 at 4:11 PM, Sebastien Goasguen <runseb@gmail.com
> >>> wrote:
> >>>
> >>>>
> >>>> On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com>
> >> wrote:
> >>>>
> >>>>> Hi Sebastien:
> >>>>>
> >>>>> Thanks!! I see the "View glossary" button just right at the
> >>>>> upper right corner of the table in this page:
> >>>>>
> >>>>> https://www.transifex.com/projects/p/ACS_DOCS/
> >>>>>
> >>>>> After entering the glossary page, I am able to select language for
> >>>> glossary
> >>>>> and add new term.
> >>>>>
> >>>>> So I'm wondering if this glossary table will be appended to the
> >> document
> >>>> or
> >>>>> it just provide the hint
> >>>>>
> >>>>> when we're translating?
> >>>>
> >>>> We are not using it:
> >>>>
> >>>> http://help.transifex.com/features/glossary.html
> >>>>
> >>>> However we could to insure consistency of the translations between
> >>>> translators of the same language.
> >>>>
> >>>>
> >>>>>
> >>>>> Regards
> >>>>>
> >>>>>
> >>>>> Isaac
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <
> runseb@gmail.com
> >>>>> wrote:
> >>>>>
> >>>>>>
> >>>>>> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> Hi all:
> >>>>>>> I have a few questions and looking for help. After the documents
> >>>>>>> have been translated, can I use Transifex to review these
> documents?
> >>>>>> Cause
> >>>>>>> I noticed that some of the terminology aren't consistent during the
> >>>>>>> translation and the language sources are too large for me to
> handling
> >>>> the
> >>>>>>> review process. So I'm wondering if it is possible for a normal
> user
> >> in
> >>>>>>> Transifex to mark the sentence as reviewed and prevent from
> reviewing
> >>>> it
> >>>>>>> twice?
> >>>>>>
> >>>>>> Isaac, considering you translated 95% of the documentation in zh-TW
> I
> >>>> made
> >>>>>> you a maintainer of the ACS_DOCS
> >>>>>> You should be able to review your own translations, string by
> string.
> >>>>>>>
> >>>>>>> Another question is about the glossary, is it part of translation
> >>>> program
> >>>>>>> or a assistant mechanism to support translation?
> >>>>>>
> >>>>>> Don't know, I have never looked at the glossary. Where do you see
> it ?
> >>>>>>
> >>>>>>>
> >>>>>>> Thanks & best regards
> >>>>>>>
> >>>>>>> Isaac
> >>>>>>>
> >>>>>>>
> >>>>>>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com>
> >>>> wrote:
> >>>>>>>
> >>>>>>>> Following Milamber's guide , below process I used for
> >>>>>>>> 4.1.xmessage.properties on zh_CN:
> >>>>>>>> 1. git pull for the latest messages_zh_CN.properties
> >>>>>>>> 2. native2ascii -reverse messages_zh_CN.properties
> >>>>>>>> /tmp/zh_CN.properties.native -encoding utf8
> >>>>>>>> 3. copy to the CloudStack_UI transifex project:
> >>>>>>>> cp/tmp/zh_CN.properties.native /
> >>>>>>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> >>>>>>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> >>>>>>>> 5. Do translation on transifex, there are some untranslated items
> >> when
> >>>>>>>> syncing with en.properties
> >>>>>>>> 6. tx pull -a
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Then convert to ascii with unicode, the i18nedit tools throws
> >>>>>> exception, I
> >>>>>>>> tried native2ascii command as below and UI display correctly:
> >>>>>>>> native2ascii -encoding UTF-8 zh_CN.properties
> >>>> messages_zh_CN.properties
> >>>>>>>>
> >>>>>>>> Are the whole processes above correct or not?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <
> >>>> runseb@gmail.com
> >>>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Milamber, I made you a manager of the transifex project so you
> can
> >>>> help
> >>>>>>>>> fixing those issues.
> >>>>>>>>>
> >>>>>>>>> -sebastien
> >>>>>>>>>
> >>>>>>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org>
> >> wrote:
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> >>>>>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org>
> >>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
> >>>>>>>>>>>>> Yes, Traditional Chinese moving very quickly.
> >>>>>>>>>>>>> Hopefully, the other languages can have more contributors.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> For the UI part, I saw the characters are not recognizable
> >>>> (browser
> >>>>>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
> >>>>>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
> >>>>>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
> >>>>>>>>>>>> This screenshots shows some characters with a incorrect
> encoding
> >>>>>> (try
> >>>>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
> >>>>>> encoding
> >>>>>>>> is
> >>>>>>>>> a UTF-8, I think)
> >>>>>>>>>>>>
> >>>>>>>>>>>> With Sebgoa, we have correct all UI ressource file to have
> only
> >>>> one
> >>>>>>>>> encoding charset in this files (ASCII with unicode). The
> transifex
> >>>> data
> >>>>>>>>> isn't up-to-date.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Sebgoa, I think we must upload the last version of this (all)
> >>>>>>>>> resources files (except FR already done) from branch 4.1 to
> >>>> transifex.
> >>>>>>>>>>>> The last version of resources files is ASCII with unicode for
> >> *all
> >>>>>>>>> chars* in each file, and now transifex keep the unicode char
> (check
> >>>>>> with
> >>>>>>>> FR
> >>>>>>>>> download for use)
> >>>>>>>>>>
> >>>>>>>>>> Mistake: transifex don't support uploaded unicode chars.
> >>>>>>>>>>
> >>>>>>>>>>> The way the original workflow was:
> >>>>>>>>>>> -Upload new versions of the resources file in english
> >>>>>>>>>>> -Translators create a new language in transifex.
> >>>>>>>>>>> -Download new language resources file
> >>>>>>>>>>> -Fix encoding
> >>>>>>>>>>
> >>>>>>>>>> For the fix encoding step, we can use this (unix and JDK)
> commands
> >>>> for
> >>>>>>>>> each language:
> >>>>>>>>>>
> >>>>>>>>>> CODELANG=it_IT
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> >>>>>>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>>>>>
> >>>>>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
> >>>>>>>>>> native2ascii ${FILE_TRANSIFEX}
> /tmp/${FILE_RES}.ascii-with-unicode
> >>>>>>>>>>
> >>>>>>>>>> # sort key, add a double-backslash before the quote char ( ' ==>
> >>>> \\' )
> >>>>>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f |
> uniq
> >> |
> >>>>>> sed
> >>>>>>>>> "s/'/\\\\\\\\\'/g" >
> >>>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> >>>>>>>>>>
> >>>>>>>>>> # Define Apache Licence Header (one long line)
> >>>>>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF)
> >> under
> >>>>>>>>> one\n# or more contributor license agreements. See the NOTICE
> >>>> file\n#
> >>>>>>>>> distributed with this work for additional information\n#
> regarding
> >>>>>>>>> copyright ownership. The ASF licenses this file\n# to you under
> >> the
> >>>>>>>> Apache
> >>>>>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this
> >> file
> >>>>>>>> except
> >>>>>>>>> in compliance\n# with the License. You may obtain a copy of the
> >>>>>> License
> >>>>>>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n#Unless
> >>>>>>>>> required by applicable law or agreed to in writing,\n# software
> >>>>>>>> distributed
> >>>>>>>>> under the License is distributed on an\n# \"AS IS\" BASIS,
> WITHOUT
> >>>>>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or
> implied.
> >>>>>> See
> >>>>>>>>> the License for the\n# specific language governing permissions
> and
> >>>>>>>>> limitations\n# under the License."
> >>>>>>>>>>
> >>>>>>>>>> # Re-introduce the AL2 header
> >>>>>>>>>> echo -e "$AL2_STRING" | cat -
> >>>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
> >>>>>>>>> ./FOR_REPO_${FILE_RES}
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> So I never uploaded the language specific resource file to
> >>>> transifex.
> >>>>>>>>> Won't we have a problem that they won't stay in sync with the
> en-US
> >>>>>>>>> resource file, if it gets changed ?
> >>>>>>>>>>
> >>>>>>>>>> On upload, Transifex seems only get the matching key with source
> >>>>>>>>> language.
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> In any case I uploaded the ja-JP resource file and the result
> on
> >>>>>>>>> transifex is less than optimal, check the unreviewed strings,
> there
> >>>> is
> >>>>>> a
> >>>>>>>>> mix of encoding.
> >>>>>>>>>>
> >>>>>>>>>> We needs to revert the native to ascii convert.
> >>>>>>>>>> We can use this steps for each language before uploading on
> >>>> transifex
> >>>>>> :
> >>>>>>>>>>
> >>>>>>>>>> CODELANG=ja
> >>>>>>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>>>>>
> >>>>>>>>>> # Revert convert
> >>>>>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> >>>>>>>>>>
> >>>>>>>>>> # Remove double backslashes before quote
> >>>>>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 >
> ${FILE_RES}.native
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> I've tested this commandes for download/upload with French
> >> language,
> >>>>>>>> and
> >>>>>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> I can make one shell script to automate this, and put in a tools
> >> dir
> >>>>>> in
> >>>>>>>>> CS git repo.
> >>>>>>>>>>
> >>>>>>>>>> Milamber
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> Milamber
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> The other languages are ok.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
> >>>>>>>> runseb@gmail.com
> >>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> There has been some terrific progress on the translations.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The easiest way to share it is to check the Transifex
> >> dashboard,
> >>>>>>>>> below are
> >>>>>>>>>>>>>> some screenshots:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The runbook:
> >>>>>>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The UI:
> >>>>>>>>>>>>>> http://awesomescreenshot.com/089163zva2
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The entire docs set:
> >>>>>>>>>>>>>> http://awesomescreenshot.com/01c163zq63
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last
> >> 3%
> >>>> on
> >>>>>>>>> the UI
> >>>>>>>>>>>>>> translations.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Keep getting the word out, forward to friends and let's all
> >> make
> >>>>>>>>>>>>>> CloudStack a truly worldwide project.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> -Sebastien
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Gavin
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 28, 2013, at 8:33 AM, Isaac Chiang <is...@gmail.com> wrote:
> Hi all:
> The Glossary function on Transifex is quite awesome. I captured
> some screenshots for it.
>
> http://i.imgur.com/WPOcVsI.png
>
> The link above is the Glossary page on Transifex, we can add new term here.
>
> We need to determine this term is a noun, verb or something else (There is
> a combo box for it ) and corresponding translation. We can also add some
> comment of it (Avoid misunderstanding if you're co-working with someone).
>
> When you are translating on the page(link below), and if you select the the
> "Glossary" tab, the glossary tab window will show the added terms
> associated to the sentence you are translating as a hint.
>
> http://i.imgur.com/GqD07pn.png
>
> The function can avoid inconsistent problem and better started in the
> beginning of translation. I am too late for discovering this function. So
> the zh_TW's document got lots of inconsistent translation problem. And I'm
> now rebuilding the dictionary :(
>
> For your information and happy translating! :D
>
Thanks a lot Isaac, it would be great if you could write a blog about this.
> Regards
>
> Isaac
>
>
>
>
>
>
> On Wed, Apr 24, 2013 at 4:20 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
>>
>> On Apr 24, 2013, at 4:18 AM, Isaac Chiang <is...@gmail.com> wrote:
>>
>>> I Get it :) I'll investigate this function deeper to see how it can help
>>> us.
>>
>> Terrific, I was hoping you would say that :)
>>
>>>
>>> Many thanks.
>>>
>>> Isaac
>>>
>>>
>>> On Wed, Apr 24, 2013 at 4:11 PM, Sebastien Goasguen <runseb@gmail.com
>>> wrote:
>>>
>>>>
>>>> On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com>
>> wrote:
>>>>
>>>>> Hi Sebastien:
>>>>>
>>>>> Thanks!! I see the "View glossary" button just right at the
>>>>> upper right corner of the table in this page:
>>>>>
>>>>> https://www.transifex.com/projects/p/ACS_DOCS/
>>>>>
>>>>> After entering the glossary page, I am able to select language for
>>>> glossary
>>>>> and add new term.
>>>>>
>>>>> So I'm wondering if this glossary table will be appended to the
>> document
>>>> or
>>>>> it just provide the hint
>>>>>
>>>>> when we're translating?
>>>>
>>>> We are not using it:
>>>>
>>>> http://help.transifex.com/features/glossary.html
>>>>
>>>> However we could to insure consistency of the translations between
>>>> translators of the same language.
>>>>
>>>>
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>> Isaac
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <runseb@gmail.com
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> Hi all:
>>>>>>> I have a few questions and looking for help. After the documents
>>>>>>> have been translated, can I use Transifex to review these documents?
>>>>>> Cause
>>>>>>> I noticed that some of the terminology aren't consistent during the
>>>>>>> translation and the language sources are too large for me to handling
>>>> the
>>>>>>> review process. So I'm wondering if it is possible for a normal user
>> in
>>>>>>> Transifex to mark the sentence as reviewed and prevent from reviewing
>>>> it
>>>>>>> twice?
>>>>>>
>>>>>> Isaac, considering you translated 95% of the documentation in zh-TW I
>>>> made
>>>>>> you a maintainer of the ACS_DOCS
>>>>>> You should be able to review your own translations, string by string.
>>>>>>>
>>>>>>> Another question is about the glossary, is it part of translation
>>>> program
>>>>>>> or a assistant mechanism to support translation?
>>>>>>
>>>>>> Don't know, I have never looked at the glossary. Where do you see it ?
>>>>>>
>>>>>>>
>>>>>>> Thanks & best regards
>>>>>>>
>>>>>>> Isaac
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com>
>>>> wrote:
>>>>>>>
>>>>>>>> Following Milamber's guide , below process I used for
>>>>>>>> 4.1.xmessage.properties on zh_CN:
>>>>>>>> 1. git pull for the latest messages_zh_CN.properties
>>>>>>>> 2. native2ascii -reverse messages_zh_CN.properties
>>>>>>>> /tmp/zh_CN.properties.native -encoding utf8
>>>>>>>> 3. copy to the CloudStack_UI transifex project:
>>>>>>>> cp/tmp/zh_CN.properties.native /
>>>>>>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>>>>>>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>>>>>>>> 5. Do translation on transifex, there are some untranslated items
>> when
>>>>>>>> syncing with en.properties
>>>>>>>> 6. tx pull -a
>>>>>>>>
>>>>>>>>
>>>>>>>> Then convert to ascii with unicode, the i18nedit tools throws
>>>>>> exception, I
>>>>>>>> tried native2ascii command as below and UI display correctly:
>>>>>>>> native2ascii -encoding UTF-8 zh_CN.properties
>>>> messages_zh_CN.properties
>>>>>>>>
>>>>>>>> Are the whole processes above correct or not?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <
>>>> runseb@gmail.com
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Milamber, I made you a manager of the transifex project so you can
>>>> help
>>>>>>>>> fixing those issues.
>>>>>>>>>
>>>>>>>>> -sebastien
>>>>>>>>>
>>>>>>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org>
>> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org>
>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>>>>>>>
>>>>>>>>>>>>> For the UI part, I saw the characters are not recognizable
>>>> (browser
>>>>>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>>>>>>>> This screenshots shows some characters with a incorrect encoding
>>>>>> (try
>>>>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>>>>>> encoding
>>>>>>>> is
>>>>>>>>> a UTF-8, I think)
>>>>>>>>>>>>
>>>>>>>>>>>> With Sebgoa, we have correct all UI ressource file to have only
>>>> one
>>>>>>>>> encoding charset in this files (ASCII with unicode). The transifex
>>>> data
>>>>>>>>> isn't up-to-date.
>>>>>>>>>>>>
>>>>>>>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>>>>>>>> resources files (except FR already done) from branch 4.1 to
>>>> transifex.
>>>>>>>>>>>> The last version of resources files is ASCII with unicode for
>> *all
>>>>>>>>> chars* in each file, and now transifex keep the unicode char (check
>>>>>> with
>>>>>>>> FR
>>>>>>>>> download for use)
>>>>>>>>>>
>>>>>>>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>>>>>>>
>>>>>>>>>>> The way the original workflow was:
>>>>>>>>>>> -Upload new versions of the resources file in english
>>>>>>>>>>> -Translators create a new language in transifex.
>>>>>>>>>>> -Download new language resources file
>>>>>>>>>>> -Fix encoding
>>>>>>>>>>
>>>>>>>>>> For the fix encoding step, we can use this (unix and JDK) commands
>>>> for
>>>>>>>>> each language:
>>>>>>>>>>
>>>>>>>>>> CODELANG=it_IT
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>>>>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>>>>>
>>>>>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>>>>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>>>>>>>>
>>>>>>>>>> # sort key, add a double-backslash before the quote char ( ' ==>
>>>> \\' )
>>>>>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq
>> |
>>>>>> sed
>>>>>>>>> "s/'/\\\\\\\\\'/g" >
>>>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>>>>>>>>
>>>>>>>>>> # Define Apache Licence Header (one long line)
>>>>>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF)
>> under
>>>>>>>>> one\n# or more contributor license agreements. See the NOTICE
>>>> file\n#
>>>>>>>>> distributed with this work for additional information\n# regarding
>>>>>>>>> copyright ownership. The ASF licenses this file\n# to you under
>> the
>>>>>>>> Apache
>>>>>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this
>> file
>>>>>>>> except
>>>>>>>>> in compliance\n# with the License. You may obtain a copy of the
>>>>>> License
>>>>>>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>>>>>>>>> required by applicable law or agreed to in writing,\n# software
>>>>>>>> distributed
>>>>>>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>>>>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
>>>>>> See
>>>>>>>>> the License for the\n# specific language governing permissions and
>>>>>>>>> limitations\n# under the License."
>>>>>>>>>>
>>>>>>>>>> # Re-introduce the AL2 header
>>>>>>>>>> echo -e "$AL2_STRING" | cat -
>>>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
>>>>>>>>> ./FOR_REPO_${FILE_RES}
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> So I never uploaded the language specific resource file to
>>>> transifex.
>>>>>>>>> Won't we have a problem that they won't stay in sync with the en-US
>>>>>>>>> resource file, if it gets changed ?
>>>>>>>>>>
>>>>>>>>>> On upload, Transifex seems only get the matching key with source
>>>>>>>>> language.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> In any case I uploaded the ja-JP resource file and the result on
>>>>>>>>> transifex is less than optimal, check the unreviewed strings, there
>>>> is
>>>>>> a
>>>>>>>>> mix of encoding.
>>>>>>>>>>
>>>>>>>>>> We needs to revert the native to ascii convert.
>>>>>>>>>> We can use this steps for each language before uploading on
>>>> transifex
>>>>>> :
>>>>>>>>>>
>>>>>>>>>> CODELANG=ja
>>>>>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>>>>>
>>>>>>>>>> # Revert convert
>>>>>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>>>>>>>
>>>>>>>>>> # Remove double backslashes before quote
>>>>>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I've tested this commandes for download/upload with French
>> language,
>>>>>>>> and
>>>>>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I can make one shell script to automate this, and put in a tools
>> dir
>>>>>> in
>>>>>>>>> CS git repo.
>>>>>>>>>>
>>>>>>>>>> Milamber
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Milamber
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> The other languages are ok.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>>>>>>>> runseb@gmail.com
>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The easiest way to share it is to check the Transifex
>> dashboard,
>>>>>>>>> below are
>>>>>>>>>>>>>> some screenshots:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The runbook:
>>>>>>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The UI:
>>>>>>>>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The entire docs set:
>>>>>>>>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last
>> 3%
>>>> on
>>>>>>>>> the UI
>>>>>>>>>>>>>> translations.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Keep getting the word out, forward to friends and let's all
>> make
>>>>>>>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Sebastien
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Gavin
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Isaac Chiang <is...@gmail.com>.
Hi all:
The Glossary function on Transifex is quite awesome. I captured
some screenshots for it.
http://i.imgur.com/WPOcVsI.png
The link above is the Glossary page on Transifex, we can add new term here.
We need to determine this term is a noun, verb or something else (There is
a combo box for it ) and corresponding translation. We can also add some
comment of it (Avoid misunderstanding if you're co-working with someone).
When you are translating on the page(link below), and if you select the the
"Glossary" tab, the glossary tab window will show the added terms
associated to the sentence you are translating as a hint.
http://i.imgur.com/GqD07pn.png
The function can avoid inconsistent problem and better started in the
beginning of translation. I am too late for discovering this function. So
the zh_TW's document got lots of inconsistent translation problem. And I'm
now rebuilding the dictionary :(
For your information and happy translating! :D
Regards
Isaac
On Wed, Apr 24, 2013 at 4:20 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Apr 24, 2013, at 4:18 AM, Isaac Chiang <is...@gmail.com> wrote:
>
> > I Get it :) I'll investigate this function deeper to see how it can help
> > us.
>
> Terrific, I was hoping you would say that :)
>
> >
> > Many thanks.
> >
> > Isaac
> >
> >
> > On Wed, Apr 24, 2013 at 4:11 PM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
> >
> >>
> >> On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com>
> wrote:
> >>
> >>> Hi Sebastien:
> >>>
> >>> Thanks!! I see the "View glossary" button just right at the
> >>> upper right corner of the table in this page:
> >>>
> >>> https://www.transifex.com/projects/p/ACS_DOCS/
> >>>
> >>> After entering the glossary page, I am able to select language for
> >> glossary
> >>> and add new term.
> >>>
> >>> So I'm wondering if this glossary table will be appended to the
> document
> >> or
> >>> it just provide the hint
> >>>
> >>> when we're translating?
> >>
> >> We are not using it:
> >>
> >> http://help.transifex.com/features/glossary.html
> >>
> >> However we could to insure consistency of the translations between
> >> translators of the same language.
> >>
> >>
> >>>
> >>> Regards
> >>>
> >>>
> >>> Isaac
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <runseb@gmail.com
> >>> wrote:
> >>>
> >>>>
> >>>> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com>
> >> wrote:
> >>>>
> >>>>> Hi all:
> >>>>> I have a few questions and looking for help. After the documents
> >>>>> have been translated, can I use Transifex to review these documents?
> >>>> Cause
> >>>>> I noticed that some of the terminology aren't consistent during the
> >>>>> translation and the language sources are too large for me to handling
> >> the
> >>>>> review process. So I'm wondering if it is possible for a normal user
> in
> >>>>> Transifex to mark the sentence as reviewed and prevent from reviewing
> >> it
> >>>>> twice?
> >>>>
> >>>> Isaac, considering you translated 95% of the documentation in zh-TW I
> >> made
> >>>> you a maintainer of the ACS_DOCS
> >>>> You should be able to review your own translations, string by string.
> >>>>>
> >>>>> Another question is about the glossary, is it part of translation
> >> program
> >>>>> or a assistant mechanism to support translation?
> >>>>
> >>>> Don't know, I have never looked at the glossary. Where do you see it ?
> >>>>
> >>>>>
> >>>>> Thanks & best regards
> >>>>>
> >>>>> Isaac
> >>>>>
> >>>>>
> >>>>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com>
> >> wrote:
> >>>>>
> >>>>>> Following Milamber's guide , below process I used for
> >>>>>> 4.1.xmessage.properties on zh_CN:
> >>>>>> 1. git pull for the latest messages_zh_CN.properties
> >>>>>> 2. native2ascii -reverse messages_zh_CN.properties
> >>>>>> /tmp/zh_CN.properties.native -encoding utf8
> >>>>>> 3. copy to the CloudStack_UI transifex project:
> >>>>>> cp/tmp/zh_CN.properties.native /
> >>>>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> >>>>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> >>>>>> 5. Do translation on transifex, there are some untranslated items
> when
> >>>>>> syncing with en.properties
> >>>>>> 6. tx pull -a
> >>>>>>
> >>>>>>
> >>>>>> Then convert to ascii with unicode, the i18nedit tools throws
> >>>> exception, I
> >>>>>> tried native2ascii command as below and UI display correctly:
> >>>>>> native2ascii -encoding UTF-8 zh_CN.properties
> >> messages_zh_CN.properties
> >>>>>>
> >>>>>> Are the whole processes above correct or not?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <
> >> runseb@gmail.com
> >>>>>>> wrote:
> >>>>>>
> >>>>>>> Milamber, I made you a manager of the transifex project so you can
> >> help
> >>>>>>> fixing those issues.
> >>>>>>>
> >>>>>>> -sebastien
> >>>>>>>
> >>>>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org>
> wrote:
> >>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> >>>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org>
> >> wrote:
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
> >>>>>>>>>>> Yes, Traditional Chinese moving very quickly.
> >>>>>>>>>>> Hopefully, the other languages can have more contributors.
> >>>>>>>>>>>
> >>>>>>>>>>> For the UI part, I saw the characters are not recognizable
> >> (browser
> >>>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
> >>>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
> >>>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
> >>>>>>>>>> This screenshots shows some characters with a incorrect encoding
> >>>> (try
> >>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
> >>>> encoding
> >>>>>> is
> >>>>>>> a UTF-8, I think)
> >>>>>>>>>>
> >>>>>>>>>> With Sebgoa, we have correct all UI ressource file to have only
> >> one
> >>>>>>> encoding charset in this files (ASCII with unicode). The transifex
> >> data
> >>>>>>> isn't up-to-date.
> >>>>>>>>>>
> >>>>>>>>>> Sebgoa, I think we must upload the last version of this (all)
> >>>>>>> resources files (except FR already done) from branch 4.1 to
> >> transifex.
> >>>>>>>>>> The last version of resources files is ASCII with unicode for
> *all
> >>>>>>> chars* in each file, and now transifex keep the unicode char (check
> >>>> with
> >>>>>> FR
> >>>>>>> download for use)
> >>>>>>>>
> >>>>>>>> Mistake: transifex don't support uploaded unicode chars.
> >>>>>>>>
> >>>>>>>>> The way the original workflow was:
> >>>>>>>>> -Upload new versions of the resources file in english
> >>>>>>>>> -Translators create a new language in transifex.
> >>>>>>>>> -Download new language resources file
> >>>>>>>>> -Fix encoding
> >>>>>>>>
> >>>>>>>> For the fix encoding step, we can use this (unix and JDK) commands
> >> for
> >>>>>>> each language:
> >>>>>>>>
> >>>>>>>> CODELANG=it_IT
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>
> >>
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> >>>>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>>>
> >>>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
> >>>>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
> >>>>>>>>
> >>>>>>>> # sort key, add a double-backslash before the quote char ( ' ==>
> >> \\' )
> >>>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq
> |
> >>>> sed
> >>>>>>> "s/'/\\\\\\\\\'/g" >
> >>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> >>>>>>>>
> >>>>>>>> # Define Apache Licence Header (one long line)
> >>>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF)
> under
> >>>>>>> one\n# or more contributor license agreements. See the NOTICE
> >> file\n#
> >>>>>>> distributed with this work for additional information\n# regarding
> >>>>>>> copyright ownership. The ASF licenses this file\n# to you under
> the
> >>>>>> Apache
> >>>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this
> file
> >>>>>> except
> >>>>>>> in compliance\n# with the License. You may obtain a copy of the
> >>>> License
> >>>>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
> >>>>>>> required by applicable law or agreed to in writing,\n# software
> >>>>>> distributed
> >>>>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
> >>>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
> >>>> See
> >>>>>>> the License for the\n# specific language governing permissions and
> >>>>>>> limitations\n# under the License."
> >>>>>>>>
> >>>>>>>> # Re-introduce the AL2 header
> >>>>>>>> echo -e "$AL2_STRING" | cat -
> >>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
> >>>>>>> ./FOR_REPO_${FILE_RES}
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> So I never uploaded the language specific resource file to
> >> transifex.
> >>>>>>> Won't we have a problem that they won't stay in sync with the en-US
> >>>>>>> resource file, if it gets changed ?
> >>>>>>>>
> >>>>>>>> On upload, Transifex seems only get the matching key with source
> >>>>>>> language.
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> In any case I uploaded the ja-JP resource file and the result on
> >>>>>>> transifex is less than optimal, check the unreviewed strings, there
> >> is
> >>>> a
> >>>>>>> mix of encoding.
> >>>>>>>>
> >>>>>>>> We needs to revert the native to ascii convert.
> >>>>>>>> We can use this steps for each language before uploading on
> >> transifex
> >>>> :
> >>>>>>>>
> >>>>>>>> CODELANG=ja
> >>>>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>>>
> >>>>>>>> # Revert convert
> >>>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> >>>>>>>>
> >>>>>>>> # Remove double backslashes before quote
> >>>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I've tested this commandes for download/upload with French
> language,
> >>>>>> and
> >>>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I can make one shell script to automate this, and put in a tools
> dir
> >>>> in
> >>>>>>> CS git repo.
> >>>>>>>>
> >>>>>>>> Milamber
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Milamber
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> The other languages are ok.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
> >>>>>> runseb@gmail.com
> >>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Hi,
> >>>>>>>>>>>>
> >>>>>>>>>>>> There has been some terrific progress on the translations.
> >>>>>>>>>>>>
> >>>>>>>>>>>> The easiest way to share it is to check the Transifex
> dashboard,
> >>>>>>> below are
> >>>>>>>>>>>> some screenshots:
> >>>>>>>>>>>>
> >>>>>>>>>>>> The runbook:
> >>>>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
> >>>>>>>>>>>>
> >>>>>>>>>>>> The UI:
> >>>>>>>>>>>> http://awesomescreenshot.com/089163zva2
> >>>>>>>>>>>>
> >>>>>>>>>>>> The entire docs set:
> >>>>>>>>>>>> http://awesomescreenshot.com/01c163zq63
> >>>>>>>>>>>>
> >>>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last
> 3%
> >> on
> >>>>>>> the UI
> >>>>>>>>>>>> translations.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Keep getting the word out, forward to friends and let's all
> make
> >>>>>>>>>>>> CloudStack a truly worldwide project.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>
> >>>>>>>>>>>> -Sebastien
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Gavin
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Isaac Chiang <is...@gmail.com>.
Hi Sebastien:
May I join the Runbook project too? I wanna make an overall
review for these two documents, thanks.
Regards
On Wed, Apr 24, 2013 at 4:20 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Apr 24, 2013, at 4:18 AM, Isaac Chiang <is...@gmail.com> wrote:
>
> > I Get it :) I'll investigate this function deeper to see how it can help
> > us.
>
> Terrific, I was hoping you would say that :)
>
> >
> > Many thanks.
> >
> > Isaac
> >
> >
> > On Wed, Apr 24, 2013 at 4:11 PM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
> >
> >>
> >> On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com>
> wrote:
> >>
> >>> Hi Sebastien:
> >>>
> >>> Thanks!! I see the "View glossary" button just right at the
> >>> upper right corner of the table in this page:
> >>>
> >>> https://www.transifex.com/projects/p/ACS_DOCS/
> >>>
> >>> After entering the glossary page, I am able to select language for
> >> glossary
> >>> and add new term.
> >>>
> >>> So I'm wondering if this glossary table will be appended to the
> document
> >> or
> >>> it just provide the hint
> >>>
> >>> when we're translating?
> >>
> >> We are not using it:
> >>
> >> http://help.transifex.com/features/glossary.html
> >>
> >> However we could to insure consistency of the translations between
> >> translators of the same language.
> >>
> >>
> >>>
> >>> Regards
> >>>
> >>>
> >>> Isaac
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <runseb@gmail.com
> >>> wrote:
> >>>
> >>>>
> >>>> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com>
> >> wrote:
> >>>>
> >>>>> Hi all:
> >>>>> I have a few questions and looking for help. After the documents
> >>>>> have been translated, can I use Transifex to review these documents?
> >>>> Cause
> >>>>> I noticed that some of the terminology aren't consistent during the
> >>>>> translation and the language sources are too large for me to handling
> >> the
> >>>>> review process. So I'm wondering if it is possible for a normal user
> in
> >>>>> Transifex to mark the sentence as reviewed and prevent from reviewing
> >> it
> >>>>> twice?
> >>>>
> >>>> Isaac, considering you translated 95% of the documentation in zh-TW I
> >> made
> >>>> you a maintainer of the ACS_DOCS
> >>>> You should be able to review your own translations, string by string.
> >>>>>
> >>>>> Another question is about the glossary, is it part of translation
> >> program
> >>>>> or a assistant mechanism to support translation?
> >>>>
> >>>> Don't know, I have never looked at the glossary. Where do you see it ?
> >>>>
> >>>>>
> >>>>> Thanks & best regards
> >>>>>
> >>>>> Isaac
> >>>>>
> >>>>>
> >>>>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com>
> >> wrote:
> >>>>>
> >>>>>> Following Milamber's guide , below process I used for
> >>>>>> 4.1.xmessage.properties on zh_CN:
> >>>>>> 1. git pull for the latest messages_zh_CN.properties
> >>>>>> 2. native2ascii -reverse messages_zh_CN.properties
> >>>>>> /tmp/zh_CN.properties.native -encoding utf8
> >>>>>> 3. copy to the CloudStack_UI transifex project:
> >>>>>> cp/tmp/zh_CN.properties.native /
> >>>>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> >>>>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> >>>>>> 5. Do translation on transifex, there are some untranslated items
> when
> >>>>>> syncing with en.properties
> >>>>>> 6. tx pull -a
> >>>>>>
> >>>>>>
> >>>>>> Then convert to ascii with unicode, the i18nedit tools throws
> >>>> exception, I
> >>>>>> tried native2ascii command as below and UI display correctly:
> >>>>>> native2ascii -encoding UTF-8 zh_CN.properties
> >> messages_zh_CN.properties
> >>>>>>
> >>>>>> Are the whole processes above correct or not?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <
> >> runseb@gmail.com
> >>>>>>> wrote:
> >>>>>>
> >>>>>>> Milamber, I made you a manager of the transifex project so you can
> >> help
> >>>>>>> fixing those issues.
> >>>>>>>
> >>>>>>> -sebastien
> >>>>>>>
> >>>>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org>
> wrote:
> >>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> >>>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org>
> >> wrote:
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
> >>>>>>>>>>> Yes, Traditional Chinese moving very quickly.
> >>>>>>>>>>> Hopefully, the other languages can have more contributors.
> >>>>>>>>>>>
> >>>>>>>>>>> For the UI part, I saw the characters are not recognizable
> >> (browser
> >>>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
> >>>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
> >>>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
> >>>>>>>>>> This screenshots shows some characters with a incorrect encoding
> >>>> (try
> >>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
> >>>> encoding
> >>>>>> is
> >>>>>>> a UTF-8, I think)
> >>>>>>>>>>
> >>>>>>>>>> With Sebgoa, we have correct all UI ressource file to have only
> >> one
> >>>>>>> encoding charset in this files (ASCII with unicode). The transifex
> >> data
> >>>>>>> isn't up-to-date.
> >>>>>>>>>>
> >>>>>>>>>> Sebgoa, I think we must upload the last version of this (all)
> >>>>>>> resources files (except FR already done) from branch 4.1 to
> >> transifex.
> >>>>>>>>>> The last version of resources files is ASCII with unicode for
> *all
> >>>>>>> chars* in each file, and now transifex keep the unicode char (check
> >>>> with
> >>>>>> FR
> >>>>>>> download for use)
> >>>>>>>>
> >>>>>>>> Mistake: transifex don't support uploaded unicode chars.
> >>>>>>>>
> >>>>>>>>> The way the original workflow was:
> >>>>>>>>> -Upload new versions of the resources file in english
> >>>>>>>>> -Translators create a new language in transifex.
> >>>>>>>>> -Download new language resources file
> >>>>>>>>> -Fix encoding
> >>>>>>>>
> >>>>>>>> For the fix encoding step, we can use this (unix and JDK) commands
> >> for
> >>>>>>> each language:
> >>>>>>>>
> >>>>>>>> CODELANG=it_IT
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>
> >>
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> >>>>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>>>
> >>>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
> >>>>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
> >>>>>>>>
> >>>>>>>> # sort key, add a double-backslash before the quote char ( ' ==>
> >> \\' )
> >>>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq
> |
> >>>> sed
> >>>>>>> "s/'/\\\\\\\\\'/g" >
> >>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> >>>>>>>>
> >>>>>>>> # Define Apache Licence Header (one long line)
> >>>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF)
> under
> >>>>>>> one\n# or more contributor license agreements. See the NOTICE
> >> file\n#
> >>>>>>> distributed with this work for additional information\n# regarding
> >>>>>>> copyright ownership. The ASF licenses this file\n# to you under
> the
> >>>>>> Apache
> >>>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this
> file
> >>>>>> except
> >>>>>>> in compliance\n# with the License. You may obtain a copy of the
> >>>> License
> >>>>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
> >>>>>>> required by applicable law or agreed to in writing,\n# software
> >>>>>> distributed
> >>>>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
> >>>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
> >>>> See
> >>>>>>> the License for the\n# specific language governing permissions and
> >>>>>>> limitations\n# under the License."
> >>>>>>>>
> >>>>>>>> # Re-introduce the AL2 header
> >>>>>>>> echo -e "$AL2_STRING" | cat -
> >>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
> >>>>>>> ./FOR_REPO_${FILE_RES}
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> So I never uploaded the language specific resource file to
> >> transifex.
> >>>>>>> Won't we have a problem that they won't stay in sync with the en-US
> >>>>>>> resource file, if it gets changed ?
> >>>>>>>>
> >>>>>>>> On upload, Transifex seems only get the matching key with source
> >>>>>>> language.
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> In any case I uploaded the ja-JP resource file and the result on
> >>>>>>> transifex is less than optimal, check the unreviewed strings, there
> >> is
> >>>> a
> >>>>>>> mix of encoding.
> >>>>>>>>
> >>>>>>>> We needs to revert the native to ascii convert.
> >>>>>>>> We can use this steps for each language before uploading on
> >> transifex
> >>>> :
> >>>>>>>>
> >>>>>>>> CODELANG=ja
> >>>>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>>>
> >>>>>>>> # Revert convert
> >>>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> >>>>>>>>
> >>>>>>>> # Remove double backslashes before quote
> >>>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I've tested this commandes for download/upload with French
> language,
> >>>>>> and
> >>>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I can make one shell script to automate this, and put in a tools
> dir
> >>>> in
> >>>>>>> CS git repo.
> >>>>>>>>
> >>>>>>>> Milamber
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Milamber
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> The other languages are ok.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
> >>>>>> runseb@gmail.com
> >>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Hi,
> >>>>>>>>>>>>
> >>>>>>>>>>>> There has been some terrific progress on the translations.
> >>>>>>>>>>>>
> >>>>>>>>>>>> The easiest way to share it is to check the Transifex
> dashboard,
> >>>>>>> below are
> >>>>>>>>>>>> some screenshots:
> >>>>>>>>>>>>
> >>>>>>>>>>>> The runbook:
> >>>>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
> >>>>>>>>>>>>
> >>>>>>>>>>>> The UI:
> >>>>>>>>>>>> http://awesomescreenshot.com/089163zva2
> >>>>>>>>>>>>
> >>>>>>>>>>>> The entire docs set:
> >>>>>>>>>>>> http://awesomescreenshot.com/01c163zq63
> >>>>>>>>>>>>
> >>>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last
> 3%
> >> on
> >>>>>>> the UI
> >>>>>>>>>>>> translations.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Keep getting the word out, forward to friends and let's all
> make
> >>>>>>>>>>>> CloudStack a truly worldwide project.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>
> >>>>>>>>>>>> -Sebastien
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Gavin
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 24, 2013, at 4:18 AM, Isaac Chiang <is...@gmail.com> wrote:
> I Get it :) I'll investigate this function deeper to see how it can help
> us.
Terrific, I was hoping you would say that :)
>
> Many thanks.
>
> Isaac
>
>
> On Wed, Apr 24, 2013 at 4:11 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
>>
>> On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com> wrote:
>>
>>> Hi Sebastien:
>>>
>>> Thanks!! I see the "View glossary" button just right at the
>>> upper right corner of the table in this page:
>>>
>>> https://www.transifex.com/projects/p/ACS_DOCS/
>>>
>>> After entering the glossary page, I am able to select language for
>> glossary
>>> and add new term.
>>>
>>> So I'm wondering if this glossary table will be appended to the document
>> or
>>> it just provide the hint
>>>
>>> when we're translating?
>>
>> We are not using it:
>>
>> http://help.transifex.com/features/glossary.html
>>
>> However we could to insure consistency of the translations between
>> translators of the same language.
>>
>>
>>>
>>> Regards
>>>
>>>
>>> Isaac
>>>
>>>
>>>
>>>
>>> On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <runseb@gmail.com
>>> wrote:
>>>
>>>>
>>>> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com>
>> wrote:
>>>>
>>>>> Hi all:
>>>>> I have a few questions and looking for help. After the documents
>>>>> have been translated, can I use Transifex to review these documents?
>>>> Cause
>>>>> I noticed that some of the terminology aren't consistent during the
>>>>> translation and the language sources are too large for me to handling
>> the
>>>>> review process. So I'm wondering if it is possible for a normal user in
>>>>> Transifex to mark the sentence as reviewed and prevent from reviewing
>> it
>>>>> twice?
>>>>
>>>> Isaac, considering you translated 95% of the documentation in zh-TW I
>> made
>>>> you a maintainer of the ACS_DOCS
>>>> You should be able to review your own translations, string by string.
>>>>>
>>>>> Another question is about the glossary, is it part of translation
>> program
>>>>> or a assistant mechanism to support translation?
>>>>
>>>> Don't know, I have never looked at the glossary. Where do you see it ?
>>>>
>>>>>
>>>>> Thanks & best regards
>>>>>
>>>>> Isaac
>>>>>
>>>>>
>>>>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com>
>> wrote:
>>>>>
>>>>>> Following Milamber's guide , below process I used for
>>>>>> 4.1.xmessage.properties on zh_CN:
>>>>>> 1. git pull for the latest messages_zh_CN.properties
>>>>>> 2. native2ascii -reverse messages_zh_CN.properties
>>>>>> /tmp/zh_CN.properties.native -encoding utf8
>>>>>> 3. copy to the CloudStack_UI transifex project:
>>>>>> cp/tmp/zh_CN.properties.native /
>>>>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>>>>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>>>>>> 5. Do translation on transifex, there are some untranslated items when
>>>>>> syncing with en.properties
>>>>>> 6. tx pull -a
>>>>>>
>>>>>>
>>>>>> Then convert to ascii with unicode, the i18nedit tools throws
>>>> exception, I
>>>>>> tried native2ascii command as below and UI display correctly:
>>>>>> native2ascii -encoding UTF-8 zh_CN.properties
>> messages_zh_CN.properties
>>>>>>
>>>>>> Are the whole processes above correct or not?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <
>> runseb@gmail.com
>>>>>>> wrote:
>>>>>>
>>>>>>> Milamber, I made you a manager of the transifex project so you can
>> help
>>>>>>> fixing those issues.
>>>>>>>
>>>>>>> -sebastien
>>>>>>>
>>>>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org>
>> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>>>>>
>>>>>>>>>>> For the UI part, I saw the characters are not recognizable
>> (browser
>>>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>>>>>> This screenshots shows some characters with a incorrect encoding
>>>> (try
>>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>>>> encoding
>>>>>> is
>>>>>>> a UTF-8, I think)
>>>>>>>>>>
>>>>>>>>>> With Sebgoa, we have correct all UI ressource file to have only
>> one
>>>>>>> encoding charset in this files (ASCII with unicode). The transifex
>> data
>>>>>>> isn't up-to-date.
>>>>>>>>>>
>>>>>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>>>>>> resources files (except FR already done) from branch 4.1 to
>> transifex.
>>>>>>>>>> The last version of resources files is ASCII with unicode for *all
>>>>>>> chars* in each file, and now transifex keep the unicode char (check
>>>> with
>>>>>> FR
>>>>>>> download for use)
>>>>>>>>
>>>>>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>>>>>
>>>>>>>>> The way the original workflow was:
>>>>>>>>> -Upload new versions of the resources file in english
>>>>>>>>> -Translators create a new language in transifex.
>>>>>>>>> -Download new language resources file
>>>>>>>>> -Fix encoding
>>>>>>>>
>>>>>>>> For the fix encoding step, we can use this (unix and JDK) commands
>> for
>>>>>>> each language:
>>>>>>>>
>>>>>>>> CODELANG=it_IT
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>>>
>>>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>>>>>>
>>>>>>>> # sort key, add a double-backslash before the quote char ( ' ==>
>> \\' )
>>>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq |
>>>> sed
>>>>>>> "s/'/\\\\\\\\\'/g" >
>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>>>>>>
>>>>>>>> # Define Apache Licence Header (one long line)
>>>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>>>>>> one\n# or more contributor license agreements. See the NOTICE
>> file\n#
>>>>>>> distributed with this work for additional information\n# regarding
>>>>>>> copyright ownership. The ASF licenses this file\n# to you under the
>>>>>> Apache
>>>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
>>>>>> except
>>>>>>> in compliance\n# with the License. You may obtain a copy of the
>>>> License
>>>>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>>>>>>> required by applicable law or agreed to in writing,\n# software
>>>>>> distributed
>>>>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
>>>> See
>>>>>>> the License for the\n# specific language governing permissions and
>>>>>>> limitations\n# under the License."
>>>>>>>>
>>>>>>>> # Re-introduce the AL2 header
>>>>>>>> echo -e "$AL2_STRING" | cat -
>>>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
>>>>>>> ./FOR_REPO_${FILE_RES}
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> So I never uploaded the language specific resource file to
>> transifex.
>>>>>>> Won't we have a problem that they won't stay in sync with the en-US
>>>>>>> resource file, if it gets changed ?
>>>>>>>>
>>>>>>>> On upload, Transifex seems only get the matching key with source
>>>>>>> language.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> In any case I uploaded the ja-JP resource file and the result on
>>>>>>> transifex is less than optimal, check the unreviewed strings, there
>> is
>>>> a
>>>>>>> mix of encoding.
>>>>>>>>
>>>>>>>> We needs to revert the native to ascii convert.
>>>>>>>> We can use this steps for each language before uploading on
>> transifex
>>>> :
>>>>>>>>
>>>>>>>> CODELANG=ja
>>>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>>>
>>>>>>>> # Revert convert
>>>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>>>>>
>>>>>>>> # Remove double backslashes before quote
>>>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
>>>>>>>>
>>>>>>>>
>>>>>>>> I've tested this commandes for download/upload with French language,
>>>>>> and
>>>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>>>>>
>>>>>>>>
>>>>>>>> I can make one shell script to automate this, and put in a tools dir
>>>> in
>>>>>>> CS git repo.
>>>>>>>>
>>>>>>>> Milamber
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Milamber
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> The other languages are ok.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>>>>>> runseb@gmail.com
>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>>>>>
>>>>>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>>>>>> below are
>>>>>>>>>>>> some screenshots:
>>>>>>>>>>>>
>>>>>>>>>>>> The runbook:
>>>>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>>>>>>
>>>>>>>>>>>> The UI:
>>>>>>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>>>>>>
>>>>>>>>>>>> The entire docs set:
>>>>>>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>>>>>>
>>>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3%
>> on
>>>>>>> the UI
>>>>>>>>>>>> translations.
>>>>>>>>>>>>
>>>>>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>
>>>>>>>>>>>> -Sebastien
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Gavin
>>>>>>
>>>>
>>>>
>>
>>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Isaac Chiang <is...@gmail.com>.
I Get it :) I'll investigate this function deeper to see how it can help
us.
Many thanks.
Isaac
On Wed, Apr 24, 2013 at 4:11 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com> wrote:
>
> > Hi Sebastien:
> >
> > Thanks!! I see the "View glossary" button just right at the
> > upper right corner of the table in this page:
> >
> > https://www.transifex.com/projects/p/ACS_DOCS/
> >
> > After entering the glossary page, I am able to select language for
> glossary
> > and add new term.
> >
> > So I'm wondering if this glossary table will be appended to the document
> or
> > it just provide the hint
> >
> > when we're translating?
>
> We are not using it:
>
> http://help.transifex.com/features/glossary.html
>
> However we could to insure consistency of the translations between
> translators of the same language.
>
>
> >
> > Regards
> >
> >
> > Isaac
> >
> >
> >
> >
> > On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
> >
> >>
> >> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com>
> wrote:
> >>
> >>> Hi all:
> >>> I have a few questions and looking for help. After the documents
> >>> have been translated, can I use Transifex to review these documents?
> >> Cause
> >>> I noticed that some of the terminology aren't consistent during the
> >>> translation and the language sources are too large for me to handling
> the
> >>> review process. So I'm wondering if it is possible for a normal user in
> >>> Transifex to mark the sentence as reviewed and prevent from reviewing
> it
> >>> twice?
> >>
> >> Isaac, considering you translated 95% of the documentation in zh-TW I
> made
> >> you a maintainer of the ACS_DOCS
> >> You should be able to review your own translations, string by string.
> >>>
> >>> Another question is about the glossary, is it part of translation
> program
> >>> or a assistant mechanism to support translation?
> >>
> >> Don't know, I have never looked at the glossary. Where do you see it ?
> >>
> >>>
> >>> Thanks & best regards
> >>>
> >>> Isaac
> >>>
> >>>
> >>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com>
> wrote:
> >>>
> >>>> Following Milamber's guide , below process I used for
> >>>> 4.1.xmessage.properties on zh_CN:
> >>>> 1. git pull for the latest messages_zh_CN.properties
> >>>> 2. native2ascii -reverse messages_zh_CN.properties
> >>>> /tmp/zh_CN.properties.native -encoding utf8
> >>>> 3. copy to the CloudStack_UI transifex project:
> >>>> cp/tmp/zh_CN.properties.native /
> >>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> >>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> >>>> 5. Do translation on transifex, there are some untranslated items when
> >>>> syncing with en.properties
> >>>> 6. tx pull -a
> >>>>
> >>>>
> >>>> Then convert to ascii with unicode, the i18nedit tools throws
> >> exception, I
> >>>> tried native2ascii command as below and UI display correctly:
> >>>> native2ascii -encoding UTF-8 zh_CN.properties
> messages_zh_CN.properties
> >>>>
> >>>> Are the whole processes above correct or not?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <
> runseb@gmail.com
> >>>>> wrote:
> >>>>
> >>>>> Milamber, I made you a manager of the transifex project so you can
> help
> >>>>> fixing those issues.
> >>>>>
> >>>>> -sebastien
> >>>>>
> >>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
> >>>>>
> >>>>>>
> >>>>>>
> >>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> >>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org>
> wrote:
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
> >>>>>>>>> Yes, Traditional Chinese moving very quickly.
> >>>>>>>>> Hopefully, the other languages can have more contributors.
> >>>>>>>>>
> >>>>>>>>> For the UI part, I saw the characters are not recognizable
> (browser
> >>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
> >>>>>>>>> ja: http://snag.gy/AVsbU.jpg
> >>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
> >>>>>>>> This screenshots shows some characters with a incorrect encoding
> >> (try
> >>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
> >> encoding
> >>>> is
> >>>>> a UTF-8, I think)
> >>>>>>>>
> >>>>>>>> With Sebgoa, we have correct all UI ressource file to have only
> one
> >>>>> encoding charset in this files (ASCII with unicode). The transifex
> data
> >>>>> isn't up-to-date.
> >>>>>>>>
> >>>>>>>> Sebgoa, I think we must upload the last version of this (all)
> >>>>> resources files (except FR already done) from branch 4.1 to
> transifex.
> >>>>>>>> The last version of resources files is ASCII with unicode for *all
> >>>>> chars* in each file, and now transifex keep the unicode char (check
> >> with
> >>>> FR
> >>>>> download for use)
> >>>>>>
> >>>>>> Mistake: transifex don't support uploaded unicode chars.
> >>>>>>
> >>>>>>> The way the original workflow was:
> >>>>>>> -Upload new versions of the resources file in english
> >>>>>>> -Translators create a new language in transifex.
> >>>>>>> -Download new language resources file
> >>>>>>> -Fix encoding
> >>>>>>
> >>>>>> For the fix encoding step, we can use this (unix and JDK) commands
> for
> >>>>> each language:
> >>>>>>
> >>>>>> CODELANG=it_IT
> >>>>>>
> >>>>>
> >>>>
> >>
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> >>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>
> >>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
> >>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
> >>>>>>
> >>>>>> # sort key, add a double-backslash before the quote char ( ' ==>
> \\' )
> >>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq |
> >> sed
> >>>>> "s/'/\\\\\\\\\'/g" >
> >>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> >>>>>>
> >>>>>> # Define Apache Licence Header (one long line)
> >>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
> >>>>> one\n# or more contributor license agreements. See the NOTICE
> file\n#
> >>>>> distributed with this work for additional information\n# regarding
> >>>>> copyright ownership. The ASF licenses this file\n# to you under the
> >>>> Apache
> >>>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
> >>>> except
> >>>>> in compliance\n# with the License. You may obtain a copy of the
> >> License
> >>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
> >>>>> required by applicable law or agreed to in writing,\n# software
> >>>> distributed
> >>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
> >>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
> >> See
> >>>>> the License for the\n# specific language governing permissions and
> >>>>> limitations\n# under the License."
> >>>>>>
> >>>>>> # Re-introduce the AL2 header
> >>>>>> echo -e "$AL2_STRING" | cat -
> >>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
> >>>>> ./FOR_REPO_${FILE_RES}
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> So I never uploaded the language specific resource file to
> transifex.
> >>>>> Won't we have a problem that they won't stay in sync with the en-US
> >>>>> resource file, if it gets changed ?
> >>>>>>
> >>>>>> On upload, Transifex seems only get the matching key with source
> >>>>> language.
> >>>>>>
> >>>>>>>
> >>>>>>> In any case I uploaded the ja-JP resource file and the result on
> >>>>> transifex is less than optimal, check the unreviewed strings, there
> is
> >> a
> >>>>> mix of encoding.
> >>>>>>
> >>>>>> We needs to revert the native to ascii convert.
> >>>>>> We can use this steps for each language before uploading on
> transifex
> >> :
> >>>>>>
> >>>>>> CODELANG=ja
> >>>>>> FILE_RES=messages_${CODELANG}.properties
> >>>>>>
> >>>>>> # Revert convert
> >>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> >>>>>>
> >>>>>> # Remove double backslashes before quote
> >>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
> >>>>>>
> >>>>>>
> >>>>>> I've tested this commandes for download/upload with French language,
> >>>> and
> >>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
> >>>>>>
> >>>>>>
> >>>>>> I can make one shell script to automate this, and put in a tools dir
> >> in
> >>>>> CS git repo.
> >>>>>>
> >>>>>> Milamber
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Milamber
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> The other languages are ok.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
> >>>> runseb@gmail.com
> >>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Hi,
> >>>>>>>>>>
> >>>>>>>>>> There has been some terrific progress on the translations.
> >>>>>>>>>>
> >>>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
> >>>>> below are
> >>>>>>>>>> some screenshots:
> >>>>>>>>>>
> >>>>>>>>>> The runbook:
> >>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
> >>>>>>>>>>
> >>>>>>>>>> The UI:
> >>>>>>>>>> http://awesomescreenshot.com/089163zva2
> >>>>>>>>>>
> >>>>>>>>>> The entire docs set:
> >>>>>>>>>> http://awesomescreenshot.com/01c163zq63
> >>>>>>>>>>
> >>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3%
> on
> >>>>> the UI
> >>>>>>>>>> translations.
> >>>>>>>>>>
> >>>>>>>>>> Keep getting the word out, forward to friends and let's all make
> >>>>>>>>>> CloudStack a truly worldwide project.
> >>>>>>>>>>
> >>>>>>>>>> Cheers,
> >>>>>>>>>>
> >>>>>>>>>> -Sebastien
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Gavin
> >>>>
> >>
> >>
>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 24, 2013, at 3:58 AM, Isaac Chiang <is...@gmail.com> wrote:
> Hi Sebastien:
>
> Thanks!! I see the "View glossary" button just right at the
> upper right corner of the table in this page:
>
> https://www.transifex.com/projects/p/ACS_DOCS/
>
> After entering the glossary page, I am able to select language for glossary
> and add new term.
>
> So I'm wondering if this glossary table will be appended to the document or
> it just provide the hint
>
> when we're translating?
We are not using it:
http://help.transifex.com/features/glossary.html
However we could to insure consistency of the translations between translators of the same language.
>
> Regards
>
>
> Isaac
>
>
>
>
> On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
>>
>> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com> wrote:
>>
>>> Hi all:
>>> I have a few questions and looking for help. After the documents
>>> have been translated, can I use Transifex to review these documents?
>> Cause
>>> I noticed that some of the terminology aren't consistent during the
>>> translation and the language sources are too large for me to handling the
>>> review process. So I'm wondering if it is possible for a normal user in
>>> Transifex to mark the sentence as reviewed and prevent from reviewing it
>>> twice?
>>
>> Isaac, considering you translated 95% of the documentation in zh-TW I made
>> you a maintainer of the ACS_DOCS
>> You should be able to review your own translations, string by string.
>>>
>>> Another question is about the glossary, is it part of translation program
>>> or a assistant mechanism to support translation?
>>
>> Don't know, I have never looked at the glossary. Where do you see it ?
>>
>>>
>>> Thanks & best regards
>>>
>>> Isaac
>>>
>>>
>>> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com> wrote:
>>>
>>>> Following Milamber's guide , below process I used for
>>>> 4.1.xmessage.properties on zh_CN:
>>>> 1. git pull for the latest messages_zh_CN.properties
>>>> 2. native2ascii -reverse messages_zh_CN.properties
>>>> /tmp/zh_CN.properties.native -encoding utf8
>>>> 3. copy to the CloudStack_UI transifex project:
>>>> cp/tmp/zh_CN.properties.native /
>>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>>>> 5. Do translation on transifex, there are some untranslated items when
>>>> syncing with en.properties
>>>> 6. tx pull -a
>>>>
>>>>
>>>> Then convert to ascii with unicode, the i18nedit tools throws
>> exception, I
>>>> tried native2ascii command as below and UI display correctly:
>>>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>>>
>>>> Are the whole processes above correct or not?
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <runseb@gmail.com
>>>>> wrote:
>>>>
>>>>> Milamber, I made you a manager of the transifex project so you can help
>>>>> fixing those issues.
>>>>>
>>>>> -sebastien
>>>>>
>>>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>>>
>>>>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>>>> This screenshots shows some characters with a incorrect encoding
>> (try
>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>> encoding
>>>> is
>>>>> a UTF-8, I think)
>>>>>>>>
>>>>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>>>>> encoding charset in this files (ASCII with unicode). The transifex data
>>>>> isn't up-to-date.
>>>>>>>>
>>>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>>>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>>>>> The last version of resources files is ASCII with unicode for *all
>>>>> chars* in each file, and now transifex keep the unicode char (check
>> with
>>>> FR
>>>>> download for use)
>>>>>>
>>>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>>>
>>>>>>> The way the original workflow was:
>>>>>>> -Upload new versions of the resources file in english
>>>>>>> -Translators create a new language in transifex.
>>>>>>> -Download new language resources file
>>>>>>> -Fix encoding
>>>>>>
>>>>>> For the fix encoding step, we can use this (unix and JDK) commands for
>>>>> each language:
>>>>>>
>>>>>> CODELANG=it_IT
>>>>>>
>>>>>
>>>>
>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>
>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>>>>
>>>>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq |
>> sed
>>>>> "s/'/\\\\\\\\\'/g" >
>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>>>>
>>>>>> # Define Apache Licence Header (one long line)
>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>>>> one\n# or more contributor license agreements. See the NOTICE file\n#
>>>>> distributed with this work for additional information\n# regarding
>>>>> copyright ownership. The ASF licenses this file\n# to you under the
>>>> Apache
>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
>>>> except
>>>>> in compliance\n# with the License. You may obtain a copy of the
>> License
>>>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>>>>> required by applicable law or agreed to in writing,\n# software
>>>> distributed
>>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
>> See
>>>>> the License for the\n# specific language governing permissions and
>>>>> limitations\n# under the License."
>>>>>>
>>>>>> # Re-introduce the AL2 header
>>>>>> echo -e "$AL2_STRING" | cat -
>>>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
>>>>> ./FOR_REPO_${FILE_RES}
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> So I never uploaded the language specific resource file to transifex.
>>>>> Won't we have a problem that they won't stay in sync with the en-US
>>>>> resource file, if it gets changed ?
>>>>>>
>>>>>> On upload, Transifex seems only get the matching key with source
>>>>> language.
>>>>>>
>>>>>>>
>>>>>>> In any case I uploaded the ja-JP resource file and the result on
>>>>> transifex is less than optimal, check the unreviewed strings, there is
>> a
>>>>> mix of encoding.
>>>>>>
>>>>>> We needs to revert the native to ascii convert.
>>>>>> We can use this steps for each language before uploading on transifex
>> :
>>>>>>
>>>>>> CODELANG=ja
>>>>>> FILE_RES=messages_${CODELANG}.properties
>>>>>>
>>>>>> # Revert convert
>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>>>
>>>>>> # Remove double backslashes before quote
>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
>>>>>>
>>>>>>
>>>>>> I've tested this commandes for download/upload with French language,
>>>> and
>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>>>
>>>>>>
>>>>>> I can make one shell script to automate this, and put in a tools dir
>> in
>>>>> CS git repo.
>>>>>>
>>>>>> Milamber
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Milamber
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> The other languages are ok.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>>>> runseb@gmail.com
>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>>>
>>>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>>>> below are
>>>>>>>>>> some screenshots:
>>>>>>>>>>
>>>>>>>>>> The runbook:
>>>>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>>>>
>>>>>>>>>> The UI:
>>>>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>>>>
>>>>>>>>>> The entire docs set:
>>>>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>>>>
>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>>>>> the UI
>>>>>>>>>> translations.
>>>>>>>>>>
>>>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> -Sebastien
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Gavin
>>>>
>>
>>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Isaac Chiang <is...@gmail.com>.
Hi Sebastien:
Thanks!! I see the "View glossary" button just right at the
upper right corner of the table in this page:
https://www.transifex.com/projects/p/ACS_DOCS/
After entering the glossary page, I am able to select language for glossary
and add new term.
So I'm wondering if this glossary table will be appended to the document or
it just provide the hint
when we're translating?
Regards
Isaac
On Wed, Apr 24, 2013 at 3:21 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com> wrote:
>
> > Hi all:
> > I have a few questions and looking for help. After the documents
> > have been translated, can I use Transifex to review these documents?
> Cause
> > I noticed that some of the terminology aren't consistent during the
> > translation and the language sources are too large for me to handling the
> > review process. So I'm wondering if it is possible for a normal user in
> > Transifex to mark the sentence as reviewed and prevent from reviewing it
> > twice?
>
> Isaac, considering you translated 95% of the documentation in zh-TW I made
> you a maintainer of the ACS_DOCS
> You should be able to review your own translations, string by string.
> >
> > Another question is about the glossary, is it part of translation program
> > or a assistant mechanism to support translation?
>
> Don't know, I have never looked at the glossary. Where do you see it ?
>
> >
> > Thanks & best regards
> >
> > Isaac
> >
> >
> > On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com> wrote:
> >
> >> Following Milamber's guide , below process I used for
> >> 4.1.xmessage.properties on zh_CN:
> >> 1. git pull for the latest messages_zh_CN.properties
> >> 2. native2ascii -reverse messages_zh_CN.properties
> >> /tmp/zh_CN.properties.native -encoding utf8
> >> 3. copy to the CloudStack_UI transifex project:
> >> cp/tmp/zh_CN.properties.native /
> >> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> >> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> >> 5. Do translation on transifex, there are some untranslated items when
> >> syncing with en.properties
> >> 6. tx pull -a
> >>
> >>
> >> Then convert to ascii with unicode, the i18nedit tools throws
> exception, I
> >> tried native2ascii command as below and UI display correctly:
> >> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
> >>
> >> Are the whole processes above correct or not?
> >>
> >>
> >>
> >>
> >> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <runseb@gmail.com
> >>> wrote:
> >>
> >>> Milamber, I made you a manager of the transifex project so you can help
> >>> fixing those issues.
> >>>
> >>> -sebastien
> >>>
> >>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
> >>>
> >>>>
> >>>>
> >>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> >>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
> >>>>>
> >>>>>>
> >>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
> >>>>>>> Yes, Traditional Chinese moving very quickly.
> >>>>>>> Hopefully, the other languages can have more contributors.
> >>>>>>>
> >>>>>>> For the UI part, I saw the characters are not recognizable (browser
> >>>>>>> encoding setting: auto detect& Unicode UTF-8):
> >>>>>>> ja: http://snag.gy/AVsbU.jpg
> >>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
> >>>>>> This screenshots shows some characters with a incorrect encoding
> (try
> >>> to display a char as a ISO-8859-1 (or japanese charset) but the
> encoding
> >> is
> >>> a UTF-8, I think)
> >>>>>>
> >>>>>> With Sebgoa, we have correct all UI ressource file to have only one
> >>> encoding charset in this files (ASCII with unicode). The transifex data
> >>> isn't up-to-date.
> >>>>>>
> >>>>>> Sebgoa, I think we must upload the last version of this (all)
> >>> resources files (except FR already done) from branch 4.1 to transifex.
> >>>>>> The last version of resources files is ASCII with unicode for *all
> >>> chars* in each file, and now transifex keep the unicode char (check
> with
> >> FR
> >>> download for use)
> >>>>
> >>>> Mistake: transifex don't support uploaded unicode chars.
> >>>>
> >>>>> The way the original workflow was:
> >>>>> -Upload new versions of the resources file in english
> >>>>> -Translators create a new language in transifex.
> >>>>> -Download new language resources file
> >>>>> -Fix encoding
> >>>>
> >>>> For the fix encoding step, we can use this (unix and JDK) commands for
> >>> each language:
> >>>>
> >>>> CODELANG=it_IT
> >>>>
> >>>
> >>
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> >>>> FILE_RES=messages_${CODELANG}.properties
> >>>>
> >>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
> >>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
> >>>>
> >>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
> >>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq |
> sed
> >>> "s/'/\\\\\\\\\'/g" >
> >>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> >>>>
> >>>> # Define Apache Licence Header (one long line)
> >>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
> >>> one\n# or more contributor license agreements. See the NOTICE file\n#
> >>> distributed with this work for additional information\n# regarding
> >>> copyright ownership. The ASF licenses this file\n# to you under the
> >> Apache
> >>> License, Version 2.0 (the\n# \"License\"); you may not use this file
> >> except
> >>> in compliance\n# with the License. You may obtain a copy of the
> License
> >>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
> >>> required by applicable law or agreed to in writing,\n# software
> >> distributed
> >>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
> >>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
> See
> >>> the License for the\n# specific language governing permissions and
> >>> limitations\n# under the License."
> >>>>
> >>>> # Re-introduce the AL2 header
> >>>> echo -e "$AL2_STRING" | cat -
> >>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
> >>> ./FOR_REPO_${FILE_RES}
> >>>>
> >>>>
> >>>>>
> >>>>> So I never uploaded the language specific resource file to transifex.
> >>> Won't we have a problem that they won't stay in sync with the en-US
> >>> resource file, if it gets changed ?
> >>>>
> >>>> On upload, Transifex seems only get the matching key with source
> >>> language.
> >>>>
> >>>>>
> >>>>> In any case I uploaded the ja-JP resource file and the result on
> >>> transifex is less than optimal, check the unreviewed strings, there is
> a
> >>> mix of encoding.
> >>>>
> >>>> We needs to revert the native to ascii convert.
> >>>> We can use this steps for each language before uploading on transifex
> :
> >>>>
> >>>> CODELANG=ja
> >>>> FILE_RES=messages_${CODELANG}.properties
> >>>>
> >>>> # Revert convert
> >>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> >>>>
> >>>> # Remove double backslashes before quote
> >>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
> >>>>
> >>>>
> >>>> I've tested this commandes for download/upload with French language,
> >> and
> >>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
> >>>>
> >>>>
> >>>> I can make one shell script to automate this, and put in a tools dir
> in
> >>> CS git repo.
> >>>>
> >>>> Milamber
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>
> >>>>>> Milamber
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> The other languages are ok.
> >>>>>>>
> >>>>>>>
> >>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
> >> runseb@gmail.com
> >>>> wrote:
> >>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> There has been some terrific progress on the translations.
> >>>>>>>>
> >>>>>>>> The easiest way to share it is to check the Transifex dashboard,
> >>> below are
> >>>>>>>> some screenshots:
> >>>>>>>>
> >>>>>>>> The runbook:
> >>>>>>>> http://awesomescreenshot.com/0bd163zldd
> >>>>>>>>
> >>>>>>>> The UI:
> >>>>>>>> http://awesomescreenshot.com/089163zva2
> >>>>>>>>
> >>>>>>>> The entire docs set:
> >>>>>>>> http://awesomescreenshot.com/01c163zq63
> >>>>>>>>
> >>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
> >>> the UI
> >>>>>>>> translations.
> >>>>>>>>
> >>>>>>>> Keep getting the word out, forward to friends and let's all make
> >>>>>>>> CloudStack a truly worldwide project.
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>>
> >>>>>>>> -Sebastien
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Gavin
> >>
>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 23, 2013, at 10:17 PM, Isaac Chiang <is...@gmail.com> wrote:
> Hi all:
> I have a few questions and looking for help. After the documents
> have been translated, can I use Transifex to review these documents? Cause
> I noticed that some of the terminology aren't consistent during the
> translation and the language sources are too large for me to handling the
> review process. So I'm wondering if it is possible for a normal user in
> Transifex to mark the sentence as reviewed and prevent from reviewing it
> twice?
Isaac, considering you translated 95% of the documentation in zh-TW I made you a maintainer of the ACS_DOCS
You should be able to review your own translations, string by string.
>
> Another question is about the glossary, is it part of translation program
> or a assistant mechanism to support translation?
Don't know, I have never looked at the glossary. Where do you see it ?
>
> Thanks & best regards
>
> Isaac
>
>
> On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com> wrote:
>
>> Following Milamber's guide , below process I used for
>> 4.1.xmessage.properties on zh_CN:
>> 1. git pull for the latest messages_zh_CN.properties
>> 2. native2ascii -reverse messages_zh_CN.properties
>> /tmp/zh_CN.properties.native -encoding utf8
>> 3. copy to the CloudStack_UI transifex project:
>> cp/tmp/zh_CN.properties.native /
>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>> 5. Do translation on transifex, there are some untranslated items when
>> syncing with en.properties
>> 6. tx pull -a
>>
>>
>> Then convert to ascii with unicode, the i18nedit tools throws exception, I
>> tried native2ascii command as below and UI display correctly:
>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>
>> Are the whole processes above correct or not?
>>
>>
>>
>>
>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <runseb@gmail.com
>>> wrote:
>>
>>> Milamber, I made you a manager of the transifex project so you can help
>>> fixing those issues.
>>>
>>> -sebastien
>>>
>>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
>>>
>>>>
>>>>
>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>
>>>>>>
>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>
>>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>> This screenshots shows some characters with a incorrect encoding (try
>>> to display a char as a ISO-8859-1 (or japanese charset) but the encoding
>> is
>>> a UTF-8, I think)
>>>>>>
>>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>>> encoding charset in this files (ASCII with unicode). The transifex data
>>> isn't up-to-date.
>>>>>>
>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>>> The last version of resources files is ASCII with unicode for *all
>>> chars* in each file, and now transifex keep the unicode char (check with
>> FR
>>> download for use)
>>>>
>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>
>>>>> The way the original workflow was:
>>>>> -Upload new versions of the resources file in english
>>>>> -Translators create a new language in transifex.
>>>>> -Download new language resources file
>>>>> -Fix encoding
>>>>
>>>> For the fix encoding step, we can use this (unix and JDK) commands for
>>> each language:
>>>>
>>>> CODELANG=it_IT
>>>>
>>>
>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>>> FILE_RES=messages_${CODELANG}.properties
>>>>
>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>>
>>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed
>>> "s/'/\\\\\\\\\'/g" >
>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>>
>>>> # Define Apache Licence Header (one long line)
>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>> one\n# or more contributor license agreements. See the NOTICE file\n#
>>> distributed with this work for additional information\n# regarding
>>> copyright ownership. The ASF licenses this file\n# to you under the
>> Apache
>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
>> except
>>> in compliance\n# with the License. You may obtain a copy of the License
>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>>> required by applicable law or agreed to in writing,\n# software
>> distributed
>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
>>> the License for the\n# specific language governing permissions and
>>> limitations\n# under the License."
>>>>
>>>> # Re-introduce the AL2 header
>>>> echo -e "$AL2_STRING" | cat -
>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
>>> ./FOR_REPO_${FILE_RES}
>>>>
>>>>
>>>>>
>>>>> So I never uploaded the language specific resource file to transifex.
>>> Won't we have a problem that they won't stay in sync with the en-US
>>> resource file, if it gets changed ?
>>>>
>>>> On upload, Transifex seems only get the matching key with source
>>> language.
>>>>
>>>>>
>>>>> In any case I uploaded the ja-JP resource file and the result on
>>> transifex is less than optimal, check the unreviewed strings, there is a
>>> mix of encoding.
>>>>
>>>> We needs to revert the native to ascii convert.
>>>> We can use this steps for each language before uploading on transifex :
>>>>
>>>> CODELANG=ja
>>>> FILE_RES=messages_${CODELANG}.properties
>>>>
>>>> # Revert convert
>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>
>>>> # Remove double backslashes before quote
>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
>>>>
>>>>
>>>> I've tested this commandes for download/upload with French language,
>> and
>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>
>>>>
>>>> I can make one shell script to automate this, and put in a tools dir in
>>> CS git repo.
>>>>
>>>> Milamber
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>> Milamber
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> The other languages are ok.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>> runseb@gmail.com
>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>
>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>> below are
>>>>>>>> some screenshots:
>>>>>>>>
>>>>>>>> The runbook:
>>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>>
>>>>>>>> The UI:
>>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>>
>>>>>>>> The entire docs set:
>>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>>
>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>>> the UI
>>>>>>>> translations.
>>>>>>>>
>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> -Sebastien
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> Gavin
>>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Isaac Chiang <is...@gmail.com>.
Hi all:
I have a few questions and looking for help. After the documents
have been translated, can I use Transifex to review these documents? Cause
I noticed that some of the terminology aren't consistent during the
translation and the language sources are too large for me to handling the
review process. So I'm wondering if it is possible for a normal user in
Transifex to mark the sentence as reviewed and prevent from reviewing it
twice?
Another question is about the glossary, is it part of translation program
or a assistant mechanism to support translation?
Thanks & best regards
Isaac
On Tue, Apr 23, 2013 at 9:50 PM, Gavin Lee <ga...@gmail.com> wrote:
> Following Milamber's guide , below process I used for
> 4.1.xmessage.properties on zh_CN:
> 1. git pull for the latest messages_zh_CN.properties
> 2. native2ascii -reverse messages_zh_CN.properties
> /tmp/zh_CN.properties.native -encoding utf8
> 3. copy to the CloudStack_UI transifex project:
> cp/tmp/zh_CN.properties.native /
> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> 5. Do translation on transifex, there are some untranslated items when
> syncing with en.properties
> 6. tx pull -a
>
>
> Then convert to ascii with unicode, the i18nedit tools throws exception, I
> tried native2ascii command as below and UI display correctly:
> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>
> Are the whole processes above correct or not?
>
>
>
>
> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
>
> > Milamber, I made you a manager of the transifex project so you can help
> > fixing those issues.
> >
> > -sebastien
> >
> > On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
> >
> > >
> > >
> > > Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> > >> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
> > >>
> > >>>
> > >>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
> > >>>> Yes, Traditional Chinese moving very quickly.
> > >>>> Hopefully, the other languages can have more contributors.
> > >>>>
> > >>>> For the UI part, I saw the characters are not recognizable (browser
> > >>>> encoding setting: auto detect& Unicode UTF-8):
> > >>>> ja: http://snag.gy/AVsbU.jpg
> > >>>> zh_CN: http://snag.gy/MxbBS.jpg
> > >>> This screenshots shows some characters with a incorrect encoding (try
> > to display a char as a ISO-8859-1 (or japanese charset) but the encoding
> is
> > a UTF-8, I think)
> > >>>
> > >>> With Sebgoa, we have correct all UI ressource file to have only one
> > encoding charset in this files (ASCII with unicode). The transifex data
> > isn't up-to-date.
> > >>>
> > >>> Sebgoa, I think we must upload the last version of this (all)
> > resources files (except FR already done) from branch 4.1 to transifex.
> > >>> The last version of resources files is ASCII with unicode for *all
> > chars* in each file, and now transifex keep the unicode char (check with
> FR
> > download for use)
> > >
> > > Mistake: transifex don't support uploaded unicode chars.
> > >
> > >> The way the original workflow was:
> > >> -Upload new versions of the resources file in english
> > >> -Translators create a new language in transifex.
> > >> -Download new language resources file
> > >> -Fix encoding
> > >
> > > For the fix encoding step, we can use this (unix and JDK) commands for
> > each language:
> > >
> > > CODELANG=it_IT
> > >
> >
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> > > FILE_RES=messages_${CODELANG}.properties
> > >
> > > # Convert to ascii with unicode (native2ascii is a JDK tool)
> > > native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
> > >
> > > # sort key, add a double-backslash before the quote char ( ' ==> \\' )
> > > grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed
> > "s/'/\\\\\\\\\'/g" >
> > /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> > >
> > > # Define Apache Licence Header (one long line)
> > > AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
> > one\n# or more contributor license agreements. See the NOTICE file\n#
> > distributed with this work for additional information\n# regarding
> > copyright ownership. The ASF licenses this file\n# to you under the
> Apache
> > License, Version 2.0 (the\n# \"License\"); you may not use this file
> except
> > in compliance\n# with the License. You may obtain a copy of the License
> > at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
> > required by applicable law or agreed to in writing,\n# software
> distributed
> > under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
> > WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
> > the License for the\n# specific language governing permissions and
> > limitations\n# under the License."
> > >
> > > # Re-introduce the AL2 header
> > > echo -e "$AL2_STRING" | cat -
> > /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
> > ./FOR_REPO_${FILE_RES}
> > >
> > >
> > >>
> > >> So I never uploaded the language specific resource file to transifex.
> > Won't we have a problem that they won't stay in sync with the en-US
> > resource file, if it gets changed ?
> > >
> > > On upload, Transifex seems only get the matching key with source
> > language.
> > >
> > >>
> > >> In any case I uploaded the ja-JP resource file and the result on
> > transifex is less than optimal, check the unreviewed strings, there is a
> > mix of encoding.
> > >
> > > We needs to revert the native to ascii convert.
> > > We can use this steps for each language before uploading on transifex :
> > >
> > > CODELANG=ja
> > > FILE_RES=messages_${CODELANG}.properties
> > >
> > > # Revert convert
> > > native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> > >
> > > # Remove double backslashes before quote
> > > sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
> > >
> > >
> > > I've tested this commandes for download/upload with French language,
> and
> > just for download with ko_KR, it_IT, ca, ja, pt_BR.
> > >
> > >
> > > I can make one shell script to automate this, and put in a tools dir in
> > CS git repo.
> > >
> > > Milamber
> > >
> > >
> > >
> > >
> > >
> > >>
> > >>
> > >>> Milamber
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>> The other languages are ok.
> > >>>>
> > >>>>
> > >>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
> runseb@gmail.com
> > >wrote:
> > >>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>> There has been some terrific progress on the translations.
> > >>>>>
> > >>>>> The easiest way to share it is to check the Transifex dashboard,
> > below are
> > >>>>> some screenshots:
> > >>>>>
> > >>>>> The runbook:
> > >>>>> http://awesomescreenshot.com/0bd163zldd
> > >>>>>
> > >>>>> The UI:
> > >>>>> http://awesomescreenshot.com/089163zva2
> > >>>>>
> > >>>>> The entire docs set:
> > >>>>> http://awesomescreenshot.com/01c163zq63
> > >>>>>
> > >>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
> > the UI
> > >>>>> translations.
> > >>>>>
> > >>>>> Keep getting the word out, forward to friends and let's all make
> > >>>>> CloudStack a truly worldwide project.
> > >>>>>
> > >>>>> Cheers,
> > >>>>>
> > >>>>> -Sebastien
> > >>>>
> > >>>>
> > >>
> > >
> >
> >
>
>
> --
> Gavin
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 24/04/2013 10:47, Milamber a ecrit :
>
>
> Le 24/04/2013 08:15, Sebastien Goasguen a ecrit :
>> On Apr 23, 2013, at 9:50 AM, Gavin Lee<ga...@gmail.com> wrote:
>>
>>> Following Milamber's guide , below process I used for
>>> 4.1.xmessage.properties on zh_CN:
>>> 1. git pull for the latest messages_zh_CN.properties
>>> 2. native2ascii -reverse messages_zh_CN.properties
>>> /tmp/zh_CN.properties.native -encoding utf8
>>> 3. copy to the CloudStack_UI transifex project:
>>> cp/tmp/zh_CN.properties.native /
>>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>>> 5. Do translation on transifex, there are some untranslated items when
>>> syncing with en.properties
>>> 6. tx pull -a
>>>
>>>
>>> Then convert to ascii with unicode, the i18nedit tools throws
>>> exception, I
>>> tried native2ascii command as below and UI display correctly:
>>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>>
>>> Are the whole processes above correct or not?
>>>
>> Gavin, I will differt o milamber on this one, he is working on this
>> to clean up the encoding and provide scripts that can make us go back
>> and forth between the source and transifex cleanly.
>
> Exactly, I've works on this. Please give some times to do this ;-)
>
Seb,
Works done with the new tool ./tools/transifex/sync-transifex-ui.sh.
You can read the README file into the same directory to know the usage.
Generally, when some new behavior on CS UI are made by developers, they
add some new keys/values in messages.properties and commit.
After, a sync upload source file is needs.
==>
./sync-transifex-ui.sh upload-source-language
CloudStack_UI.42xmessagesproperties
And time-to-time or after a update request by a translator, we need
download the L10N resource files in CS git tree.
==>
./sync-transifex-ui.sh download-l10n-languages
CloudStack_UI.42xmessagesproperties
Milamber
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 24/04/2013 08:15, Sebastien Goasguen a ecrit :
> On Apr 23, 2013, at 9:50 AM, Gavin Lee<ga...@gmail.com> wrote:
>
>> Following Milamber's guide , below process I used for
>> 4.1.xmessage.properties on zh_CN:
>> 1. git pull for the latest messages_zh_CN.properties
>> 2. native2ascii -reverse messages_zh_CN.properties
>> /tmp/zh_CN.properties.native -encoding utf8
>> 3. copy to the CloudStack_UI transifex project: cp/tmp/zh_CN.properties.native /
>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>> 5. Do translation on transifex, there are some untranslated items when
>> syncing with en.properties
>> 6. tx pull -a
>>
>>
>> Then convert to ascii with unicode, the i18nedit tools throws exception, I
>> tried native2ascii command as below and UI display correctly:
>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>
>> Are the whole processes above correct or not?
>>
> Gavin, I will differt o milamber on this one, he is working on this to clean up the encoding and provide scripts that can make us go back and forth between the source and transifex cleanly.
Exactly, I've works on this. Please give some times to do this ;-)
Milamber
>
>>
>>
>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen<ru...@gmail.com>wrote:
>>
>>> Milamber, I made you a manager of the transifex project so you can help
>>> fixing those issues.
>>>
>>> -sebastien
>>>
>>> On Apr 22, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>
>>>>
>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>
>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>
>>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>> This screenshots shows some characters with a incorrect encoding (try
>>> to display a char as a ISO-8859-1 (or japanese charset) but the encoding is
>>> a UTF-8, I think)
>>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>>> encoding charset in this files (ASCII with unicode). The transifex data
>>> isn't up-to-date.
>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>>> The last version of resources files is ASCII with unicode for *all
>>> chars* in each file, and now transifex keep the unicode char (check with FR
>>> download for use)
>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>
>>>>> The way the original workflow was:
>>>>> -Upload new versions of the resources file in english
>>>>> -Translators create a new language in transifex.
>>>>> -Download new language resources file
>>>>> -Fix encoding
>>>> For the fix encoding step, we can use this (unix and JDK) commands for
>>> each language:
>>>> CODELANG=it_IT
>>>>
>>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>>> FILE_RES=messages_${CODELANG}.properties
>>>>
>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>>
>>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed
>>> "s/'/\\\\\\\\\'/g">
>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>> # Define Apache Licence Header (one long line)
>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>> one\n# or more contributor license agreements. See the NOTICE file\n#
>>> distributed with this work for additional information\n# regarding
>>> copyright ownership. The ASF licenses this file\n# to you under the Apache
>>> License, Version 2.0 (the\n# \"License\"); you may not use this file except
>>> in compliance\n# with the License. You may obtain a copy of the License
>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>>> required by applicable law or agreed to in writing,\n# software distributed
>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
>>> the License for the\n# specific language governing permissions and
>>> limitations\n# under the License."
>>>> # Re-introduce the AL2 header
>>>> echo -e "$AL2_STRING" | cat -
>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote>
>>> ./FOR_REPO_${FILE_RES}
>>>>
>>>>> So I never uploaded the language specific resource file to transifex.
>>> Won't we have a problem that they won't stay in sync with the en-US
>>> resource file, if it gets changed ?
>>>> On upload, Transifex seems only get the matching key with source
>>> language.
>>>>> In any case I uploaded the ja-JP resource file and the result on
>>> transifex is less than optimal, check the unreviewed strings, there is a
>>> mix of encoding.
>>>> We needs to revert the native to ascii convert.
>>>> We can use this steps for each language before uploading on transifex :
>>>>
>>>> CODELANG=ja
>>>> FILE_RES=messages_${CODELANG}.properties
>>>>
>>>> # Revert convert
>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>
>>>> # Remove double backslashes before quote
>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1> ${FILE_RES}.native
>>>>
>>>>
>>>> I've tested this commandes for download/upload with French language, and
>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>
>>>> I can make one shell script to automate this, and put in a tools dir in
>>> CS git repo.
>>>> Milamber
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>> Milamber
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> The other languages are ok.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<runseb@gmail.com
>>>> wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>
>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>> below are
>>>>>>>> some screenshots:
>>>>>>>>
>>>>>>>> The runbook:
>>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>>
>>>>>>>> The UI:
>>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>>
>>>>>>>> The entire docs set:
>>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>>
>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>>> the UI
>>>>>>>> translations.
>>>>>>>>
>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> -Sebastien
>>>>>>>
>>>
>>
>> --
>> Gavin
> .
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 23, 2013, at 9:50 AM, Gavin Lee <ga...@gmail.com> wrote:
> Following Milamber's guide , below process I used for
> 4.1.xmessage.properties on zh_CN:
> 1. git pull for the latest messages_zh_CN.properties
> 2. native2ascii -reverse messages_zh_CN.properties
> /tmp/zh_CN.properties.native -encoding utf8
> 3. copy to the CloudStack_UI transifex project: cp/tmp/zh_CN.properties.native /
> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> 5. Do translation on transifex, there are some untranslated items when
> syncing with en.properties
> 6. tx pull -a
>
>
> Then convert to ascii with unicode, the i18nedit tools throws exception, I
> tried native2ascii command as below and UI display correctly:
> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>
> Are the whole processes above correct or not?
>
Gavin, I will differt o milamber on this one, he is working on this to clean up the encoding and provide scripts that can make us go back and forth between the source and transifex cleanly.
>
>
>
> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
>> Milamber, I made you a manager of the transifex project so you can help
>> fixing those issues.
>>
>> -sebastien
>>
>> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
>>
>>>
>>>
>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>
>>>>>
>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>
>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>> This screenshots shows some characters with a incorrect encoding (try
>> to display a char as a ISO-8859-1 (or japanese charset) but the encoding is
>> a UTF-8, I think)
>>>>>
>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>> encoding charset in this files (ASCII with unicode). The transifex data
>> isn't up-to-date.
>>>>>
>>>>> Sebgoa, I think we must upload the last version of this (all)
>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>> The last version of resources files is ASCII with unicode for *all
>> chars* in each file, and now transifex keep the unicode char (check with FR
>> download for use)
>>>
>>> Mistake: transifex don't support uploaded unicode chars.
>>>
>>>> The way the original workflow was:
>>>> -Upload new versions of the resources file in english
>>>> -Translators create a new language in transifex.
>>>> -Download new language resources file
>>>> -Fix encoding
>>>
>>> For the fix encoding step, we can use this (unix and JDK) commands for
>> each language:
>>>
>>> CODELANG=it_IT
>>>
>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>> FILE_RES=messages_${CODELANG}.properties
>>>
>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>
>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed
>> "s/'/\\\\\\\\\'/g" >
>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>
>>> # Define Apache Licence Header (one long line)
>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>> one\n# or more contributor license agreements. See the NOTICE file\n#
>> distributed with this work for additional information\n# regarding
>> copyright ownership. The ASF licenses this file\n# to you under the Apache
>> License, Version 2.0 (the\n# \"License\"); you may not use this file except
>> in compliance\n# with the License. You may obtain a copy of the License
>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>> required by applicable law or agreed to in writing,\n# software distributed
>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
>> the License for the\n# specific language governing permissions and
>> limitations\n# under the License."
>>>
>>> # Re-introduce the AL2 header
>>> echo -e "$AL2_STRING" | cat -
>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
>> ./FOR_REPO_${FILE_RES}
>>>
>>>
>>>>
>>>> So I never uploaded the language specific resource file to transifex.
>> Won't we have a problem that they won't stay in sync with the en-US
>> resource file, if it gets changed ?
>>>
>>> On upload, Transifex seems only get the matching key with source
>> language.
>>>
>>>>
>>>> In any case I uploaded the ja-JP resource file and the result on
>> transifex is less than optimal, check the unreviewed strings, there is a
>> mix of encoding.
>>>
>>> We needs to revert the native to ascii convert.
>>> We can use this steps for each language before uploading on transifex :
>>>
>>> CODELANG=ja
>>> FILE_RES=messages_${CODELANG}.properties
>>>
>>> # Revert convert
>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>
>>> # Remove double backslashes before quote
>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
>>>
>>>
>>> I've tested this commandes for download/upload with French language, and
>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>
>>>
>>> I can make one shell script to automate this, and put in a tools dir in
>> CS git repo.
>>>
>>> Milamber
>>>
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>>> Milamber
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> The other languages are ok.
>>>>>>
>>>>>>
>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<runseb@gmail.com
>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> There has been some terrific progress on the translations.
>>>>>>>
>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>> below are
>>>>>>> some screenshots:
>>>>>>>
>>>>>>> The runbook:
>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>
>>>>>>> The UI:
>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>
>>>>>>> The entire docs set:
>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>
>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>> the UI
>>>>>>> translations.
>>>>>>>
>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>> CloudStack a truly worldwide project.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> -Sebastien
>>>>>>
>>>>>>
>>>>
>>>
>>
>>
>
>
> --
> Gavin
Re: [DOCS][TRANSLATIONS] Upate
Posted by David Nalley <da...@gnsa.us>.
On Fri, Apr 26, 2013 at 11:11 AM, Milamber <mi...@apache.org> wrote:
>
> Le 26/04/2013 11:52, Sebastien Goasguen a ecrit :
>
>> On Apr 26, 2013, at 4:18 AM, Sebastien Goasguen <ru...@gmail.com> wrote:
>>
>>> On Apr 25, 2013, at 5:12 PM, Milamber <mi...@apache.org> wrote:
>>>
>>>> Le 25/04/2013 20:18, Sebastien Goasguen a ecrit :
>>>>>
>>>>> On Apr 25, 2013, at 1:54 PM, David Nalley <da...@gnsa.us> wrote:
>>>>>
>>>>>> On Thursday, April 25, 2013, Sebastien Goasguen wrote:
>>>>>>
>>>>>>> On Apr 25, 2013, at 4:48 AM, Milamber <milamber@apache.org
>>>>>>> <javascript:;>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Le 25/04/2013 08:05, Gavin Lee a ecrit :
>>>>>>>>>
>>>>>>>>> Done for zh_CN translation on transifex for master branch.
>>>>>>>>
>>>>>>>> Thanks. I just update the master branch.
>>>>>>>>
>>>>>>>>> For 2.2.xmessages for zh_CN, and also for ja, the encoding is
>>>>>>>>> incorrect
>>>>>>>
>>>>>>> and
>>>>>>>>>
>>>>>>>>> resource files are not maintained by community.
>>>>>>>>
>>>>>>>> Yes, the encoding's translation are incorrect.
>>>>>>>> I don't know where we can find the original 2.2 resource file to fix
>>>>>>>> it.
>>>>>>>
>>>>>>> But I don't if we must maintain the version 2.2…
>>>>>>>
>>>>>>> No, IMHO we should only maintain 4.x + since those are the only
>>>>>>> Apache
>>>>>>> releases.
>>>>>>>
>>>>>>> as a side note, I noticed a Apache CloudStack UL project on transifex
>>>>>>> which has 16% translation of the UI in arabic. I had met the folks in
>>>>>>> Oman,
>>>>>>> and they wanted their own project to manage. However i don't know how
>>>>>>> to
>>>>>>> "import" their translations into our project.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Can you reach out to them via email and ask them to submit it via the
>>>>>> mailing list or RB? We really need it to be voluntarily submitted
>>>>>> since
>>>>>> they did it externally to the project.
>>>>>
>>>>> I will if it's needed.
>>>>>
>>>>> There is a more problematic issue with arabic that milamber raised: the
>>>>> ui is not setup to do right to left rendering….
>>>>
>>>> Seb,
>>>>
>>>> I have make a test with success (I think) to display arabic translation
>>>> of Web UI on dashboard. (To work, need to remove one sequence "\n" in AR
>>>> resource from CS UL project)
>>>>
>>>> http://awesomescreenshot.com/07817h5gc6
>>>>
>>>> A control to word "Dashboard" (Arabic is display correctly) (even if
>>>> the alignment is not at right, the text is RTL)
>>>> http://awesomescreenshot.com/03317h5o82
>>>>
>>>> IMO, I would better to manage the arabic translation directly into CS UI
>>>> project in transifex.
>>>>
>>> I agree, I am asking them. They wanted their own project so that they
>>> could manage their team...
>>>
>>>> Milamber
>>>>
>> They have moved their strings to our apache UI project. However they not
>> show up in ASCII, something to look at.
>
>
> Fix it. I have transform the \\uXXXX char to native value.
>
> I think their transifex project has a better setup than the current CS UI
> projet. In their project, when you download the resource file, you have
> directly a ASCII w/ unicode file (not native chars like CS UI project).
> The source of issue is the choice of type when we create a new resource in
> transifex: the good choice seems Java Properties with Unicode (not Latin1)
>
> Milamber
>
Feel free to blame me for that. I know just enough about l10n to be dangerous.
I am sure the folks at Transifex could help us rectify it.
--David
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 26/04/2013 11:52, Sebastien Goasguen a ecrit :
> On Apr 26, 2013, at 4:18 AM, Sebastien Goasguen <ru...@gmail.com> wrote:
>
>> On Apr 25, 2013, at 5:12 PM, Milamber <mi...@apache.org> wrote:
>>
>>> Le 25/04/2013 20:18, Sebastien Goasguen a ecrit :
>>>> On Apr 25, 2013, at 1:54 PM, David Nalley <da...@gnsa.us> wrote:
>>>>
>>>>> On Thursday, April 25, 2013, Sebastien Goasguen wrote:
>>>>>
>>>>>> On Apr 25, 2013, at 4:48 AM, Milamber <milamber@apache.org <javascript:;>>
>>>>>> wrote:
>>>>>>
>>>>>>> Le 25/04/2013 08:05, Gavin Lee a ecrit :
>>>>>>>> Done for zh_CN translation on transifex for master branch.
>>>>>>> Thanks. I just update the master branch.
>>>>>>>
>>>>>>>> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect
>>>>>> and
>>>>>>>> resource files are not maintained by community.
>>>>>>> Yes, the encoding's translation are incorrect.
>>>>>>> I don't know where we can find the original 2.2 resource file to fix it.
>>>>>> But I don't if we must maintain the version 2.2…
>>>>>>
>>>>>> No, IMHO we should only maintain 4.x + since those are the only Apache
>>>>>> releases.
>>>>>>
>>>>>> as a side note, I noticed a Apache CloudStack UL project on transifex
>>>>>> which has 16% translation of the UI in arabic. I had met the folks in Oman,
>>>>>> and they wanted their own project to manage. However i don't know how to
>>>>>> "import" their translations into our project.
>>>>>>
>>>>>>
>>>>>>
>>>>> Can you reach out to them via email and ask them to submit it via the
>>>>> mailing list or RB? We really need it to be voluntarily submitted since
>>>>> they did it externally to the project.
>>>> I will if it's needed.
>>>>
>>>> There is a more problematic issue with arabic that milamber raised: the ui is not setup to do right to left rendering….
>>> Seb,
>>>
>>> I have make a test with success (I think) to display arabic translation of Web UI on dashboard. (To work, need to remove one sequence "\n" in AR resource from CS UL project)
>>>
>>> http://awesomescreenshot.com/07817h5gc6
>>>
>>> A control to word "Dashboard" (Arabic is display correctly) (even if the alignment is not at right, the text is RTL)
>>> http://awesomescreenshot.com/03317h5o82
>>>
>>> IMO, I would better to manage the arabic translation directly into CS UI project in transifex.
>>>
>> I agree, I am asking them. They wanted their own project so that they could manage their team...
>>
>>> Milamber
>>>
> They have moved their strings to our apache UI project. However they not show up in ASCII, something to look at.
Fix it. I have transform the \\uXXXX char to native value.
I think their transifex project has a better setup than the current CS
UI projet. In their project, when you download the resource file, you
have directly a ASCII w/ unicode file (not native chars like CS UI project).
The source of issue is the choice of type when we create a new resource
in transifex: the good choice seems Java Properties with Unicode (not
Latin1)
Milamber
>
> -sebastien
>
>>>> -sebastien
>>>>
>>>>
>>>>> --David
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 26, 2013, at 4:18 AM, Sebastien Goasguen <ru...@gmail.com> wrote:
>
> On Apr 25, 2013, at 5:12 PM, Milamber <mi...@apache.org> wrote:
>
>>
>> Le 25/04/2013 20:18, Sebastien Goasguen a ecrit :
>>> On Apr 25, 2013, at 1:54 PM, David Nalley <da...@gnsa.us> wrote:
>>>
>>>> On Thursday, April 25, 2013, Sebastien Goasguen wrote:
>>>>
>>>>> On Apr 25, 2013, at 4:48 AM, Milamber <milamber@apache.org <javascript:;>>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Le 25/04/2013 08:05, Gavin Lee a ecrit :
>>>>>>> Done for zh_CN translation on transifex for master branch.
>>>>>> Thanks. I just update the master branch.
>>>>>>
>>>>>>> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect
>>>>> and
>>>>>>> resource files are not maintained by community.
>>>>>> Yes, the encoding's translation are incorrect.
>>>>>> I don't know where we can find the original 2.2 resource file to fix it.
>>>>> But I don't if we must maintain the version 2.2…
>>>>>
>>>>> No, IMHO we should only maintain 4.x + since those are the only Apache
>>>>> releases.
>>>>>
>>>>> as a side note, I noticed a Apache CloudStack UL project on transifex
>>>>> which has 16% translation of the UI in arabic. I had met the folks in Oman,
>>>>> and they wanted their own project to manage. However i don't know how to
>>>>> "import" their translations into our project.
>>>>>
>>>>>
>>>>>
>>>> Can you reach out to them via email and ask them to submit it via the
>>>> mailing list or RB? We really need it to be voluntarily submitted since
>>>> they did it externally to the project.
>>> I will if it's needed.
>>>
>>> There is a more problematic issue with arabic that milamber raised: the ui is not setup to do right to left rendering….
>>
>> Seb,
>>
>> I have make a test with success (I think) to display arabic translation of Web UI on dashboard. (To work, need to remove one sequence "\n" in AR resource from CS UL project)
>>
>> http://awesomescreenshot.com/07817h5gc6
>>
>> A control to word "Dashboard" (Arabic is display correctly) (even if the alignment is not at right, the text is RTL)
>> http://awesomescreenshot.com/03317h5o82
>>
>> IMO, I would better to manage the arabic translation directly into CS UI project in transifex.
>>
>
> I agree, I am asking them. They wanted their own project so that they could manage their team...
>
>> Milamber
>>
They have moved their strings to our apache UI project. However they not show up in ASCII, something to look at.
-sebastien
>>>
>>> -sebastien
>>>
>>>
>>>> --David
>>>
>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 25, 2013, at 5:12 PM, Milamber <mi...@apache.org> wrote:
>
> Le 25/04/2013 20:18, Sebastien Goasguen a ecrit :
>> On Apr 25, 2013, at 1:54 PM, David Nalley <da...@gnsa.us> wrote:
>>
>>> On Thursday, April 25, 2013, Sebastien Goasguen wrote:
>>>
>>>> On Apr 25, 2013, at 4:48 AM, Milamber <milamber@apache.org <javascript:;>>
>>>> wrote:
>>>>
>>>>>
>>>>> Le 25/04/2013 08:05, Gavin Lee a ecrit :
>>>>>> Done for zh_CN translation on transifex for master branch.
>>>>> Thanks. I just update the master branch.
>>>>>
>>>>>> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect
>>>> and
>>>>>> resource files are not maintained by community.
>>>>> Yes, the encoding's translation are incorrect.
>>>>> I don't know where we can find the original 2.2 resource file to fix it.
>>>> But I don't if we must maintain the version 2.2…
>>>>
>>>> No, IMHO we should only maintain 4.x + since those are the only Apache
>>>> releases.
>>>>
>>>> as a side note, I noticed a Apache CloudStack UL project on transifex
>>>> which has 16% translation of the UI in arabic. I had met the folks in Oman,
>>>> and they wanted their own project to manage. However i don't know how to
>>>> "import" their translations into our project.
>>>>
>>>>
>>>>
>>> Can you reach out to them via email and ask them to submit it via the
>>> mailing list or RB? We really need it to be voluntarily submitted since
>>> they did it externally to the project.
>> I will if it's needed.
>>
>> There is a more problematic issue with arabic that milamber raised: the ui is not setup to do right to left rendering….
>
> Seb,
>
> I have make a test with success (I think) to display arabic translation of Web UI on dashboard. (To work, need to remove one sequence "\n" in AR resource from CS UL project)
>
> http://awesomescreenshot.com/07817h5gc6
>
> A control to word "Dashboard" (Arabic is display correctly) (even if the alignment is not at right, the text is RTL)
> http://awesomescreenshot.com/03317h5o82
>
> IMO, I would better to manage the arabic translation directly into CS UI project in transifex.
>
I agree, I am asking them. They wanted their own project so that they could manage their team...
> Milamber
>
>>
>> -sebastien
>>
>>
>>> --David
>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 25/04/2013 20:18, Sebastien Goasguen a ecrit :
> On Apr 25, 2013, at 1:54 PM, David Nalley <da...@gnsa.us> wrote:
>
>> On Thursday, April 25, 2013, Sebastien Goasguen wrote:
>>
>>> On Apr 25, 2013, at 4:48 AM, Milamber <milamber@apache.org <javascript:;>>
>>> wrote:
>>>
>>>>
>>>> Le 25/04/2013 08:05, Gavin Lee a ecrit :
>>>>> Done for zh_CN translation on transifex for master branch.
>>>> Thanks. I just update the master branch.
>>>>
>>>>> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect
>>> and
>>>>> resource files are not maintained by community.
>>>> Yes, the encoding's translation are incorrect.
>>>> I don't know where we can find the original 2.2 resource file to fix it.
>>> But I don't if we must maintain the version 2.2…
>>>
>>> No, IMHO we should only maintain 4.x + since those are the only Apache
>>> releases.
>>>
>>> as a side note, I noticed a Apache CloudStack UL project on transifex
>>> which has 16% translation of the UI in arabic. I had met the folks in Oman,
>>> and they wanted their own project to manage. However i don't know how to
>>> "import" their translations into our project.
>>>
>>>
>>>
>> Can you reach out to them via email and ask them to submit it via the
>> mailing list or RB? We really need it to be voluntarily submitted since
>> they did it externally to the project.
> I will if it's needed.
>
> There is a more problematic issue with arabic that milamber raised: the ui is not setup to do right to left rendering….
Seb,
I have make a test with success (I think) to display arabic translation
of Web UI on dashboard. (To work, need to remove one sequence "\n" in
AR resource from CS UL project)
http://awesomescreenshot.com/07817h5gc6
A control to word "Dashboard" (Arabic is display correctly) (even if
the alignment is not at right, the text is RTL)
http://awesomescreenshot.com/03317h5o82
IMO, I would better to manage the arabic translation directly into CS UI
project in transifex.
Milamber
>
> -sebastien
>
>
>> --David
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 25, 2013, at 1:54 PM, David Nalley <da...@gnsa.us> wrote:
> On Thursday, April 25, 2013, Sebastien Goasguen wrote:
>
>>
>> On Apr 25, 2013, at 4:48 AM, Milamber <milamber@apache.org <javascript:;>>
>> wrote:
>>
>>>
>>>
>>> Le 25/04/2013 08:05, Gavin Lee a ecrit :
>>>> Done for zh_CN translation on transifex for master branch.
>>>
>>> Thanks. I just update the master branch.
>>>
>>>>
>>>> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect
>> and
>>>> resource files are not maintained by community.
>>>
>>> Yes, the encoding's translation are incorrect.
>>> I don't know where we can find the original 2.2 resource file to fix it.
>> But I don't if we must maintain the version 2.2…
>>
>> No, IMHO we should only maintain 4.x + since those are the only Apache
>> releases.
>>
>> as a side note, I noticed a Apache CloudStack UL project on transifex
>> which has 16% translation of the UI in arabic. I had met the folks in Oman,
>> and they wanted their own project to manage. However i don't know how to
>> "import" their translations into our project.
>>
>>
>>
> Can you reach out to them via email and ask them to submit it via the
> mailing list or RB? We really need it to be voluntarily submitted since
> they did it externally to the project.
I will if it's needed.
There is a more problematic issue with arabic that milamber raised: the ui is not setup to do right to left rendering….
-sebastien
>
> --David
Re: [DOCS][TRANSLATIONS] Upate
Posted by David Nalley <da...@gnsa.us>.
On Thursday, April 25, 2013, Sebastien Goasguen wrote:
>
> On Apr 25, 2013, at 4:48 AM, Milamber <milamber@apache.org <javascript:;>>
> wrote:
>
> >
> >
> > Le 25/04/2013 08:05, Gavin Lee a ecrit :
> >> Done for zh_CN translation on transifex for master branch.
> >
> > Thanks. I just update the master branch.
> >
> >>
> >> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect
> and
> >> resource files are not maintained by community.
> >
> > Yes, the encoding's translation are incorrect.
> > I don't know where we can find the original 2.2 resource file to fix it.
> But I don't if we must maintain the version 2.2…
>
> No, IMHO we should only maintain 4.x + since those are the only Apache
> releases.
>
> as a side note, I noticed a Apache CloudStack UL project on transifex
> which has 16% translation of the UI in arabic. I had met the folks in Oman,
> and they wanted their own project to manage. However i don't know how to
> "import" their translations into our project.
>
>
>
Can you reach out to them via email and ask them to submit it via the
mailing list or RB? We really need it to be voluntarily submitted since
they did it externally to the project.
--David
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 25, 2013, at 4:48 AM, Milamber <mi...@apache.org> wrote:
>
>
> Le 25/04/2013 08:05, Gavin Lee a ecrit :
>> Done for zh_CN translation on transifex for master branch.
>
> Thanks. I just update the master branch.
>
>>
>> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect and
>> resource files are not maintained by community.
>
> Yes, the encoding's translation are incorrect.
> I don't know where we can find the original 2.2 resource file to fix it. But I don't if we must maintain the version 2.2…
No, IMHO we should only maintain 4.x + since those are the only Apache releases.
as a side note, I noticed a Apache CloudStack UL project on transifex which has 16% translation of the UI in arabic. I had met the folks in Oman, and they wanted their own project to manage. However i don't know how to "import" their translations into our project.
>
> Milamber
>
>>
>>
>> On Wed, Apr 24, 2013 at 10:06 PM, Milamber<mi...@apache.org> wrote:
>>
>>>
>>> Le 24/04/2013 10:44, Milamber a ecrit :
>>>
>>>
>>>> Le 23/04/2013 13:50, Gavin Lee a ecrit :
>>>>
>>>>> Following Milamber's guide , below process I used for
>>>>> 4.1.xmessage.properties on zh_CN:
>>>>> 1. git pull for the latest messages_zh_CN.properties
>>>>> 2. native2ascii -reverse messages_zh_CN.properties
>>>>> /tmp/zh_CN.properties.native -encoding utf8
>>>>>
>>>> -encoding utf8<=== not necessary (on my machine)
>>>
>>>
>>> 3. copy to the CloudStack_UI transifex project:
>>>>> cp/tmp/zh_CN.properties.native /
>>>>> txprj/acsui/translations/**CloudStack_UI.**41xmessageproperties
>>>>> 4. tx push -l zh_CN -r CloudStack_UI.**41xmessageproperties -t
>>>>> 5. Do translation on transifex, there are some untranslated items when
>>>>> syncing with en.properties
>>>>> 6. tx pull -a
>>>>>
>>>>>
>>>>> Then convert to ascii with unicode, the i18nedit tools throws exception,
>>>>> I
>>>>> tried native2ascii command as below and UI display correctly:
>>>>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>>>>
>>>>> Are the whole processes above correct or not?
>>>>>
>>>> Yes the process is correct, but currently on master branch the
>>>> messages_zh_CN.properties is not converting into a ASCII with unicode
>>>> unlike the 4.1 branch.
>>>> I will fix this for all messages_xx.properties on master branch today
>>>> (tonight) (FRench is already convert)
>>>>
>>> I just have made the fix for chinese (zh_CN) resource file on master
>>> branch. Now it's a ascii with unicode file and the process can execute
>>> manually with transifex.
>>> I made too a upload on transifex (with converting into native charset) for
>>> fix all sentences which have been corrupts with a previous upload (perhaps
>>> your upload I think)
>>>
>>>
>>> Currently, missing 33 translations for master (4.2) resource file zn_CN on
>>> transifex.
>>>
>>> Milamber
>>>
>>>
>>>
>>>> === (on master branch) ===
>>>>
>>>> cloudstack-dev/client/WEB-INF/**classes/resources$ file *
>>>> messages_fr_FR.properties: ASCII text, with very long lines
>>>> messages_ja.properties: UTF-8 Unicode text, with very long lines
>>>> messages_ko_KR.properties: UTF-8 Unicode text, with very long lines
>>>> messages.properties: ASCII text, with very long lines
>>>> messages_pt_BR.properties: ISO-8859 text, with very long lines
>>>> messages_ru_RU.properties: UTF-8 Unicode text, with very long lines, with
>>>> CRLF line terminators
>>>> messages_zh_CN.properties: UTF-8 Unicode text, with very long lines, with
>>>> CRLF, LF line terminators
>>>>
>>>> === (on 4.1 branch) ===
>>>> cloudstack-dev/client/WEB-INF/**classes/resources$ file *
>>>> messages_ca.properties: ASCII text, with very long lines
>>>> messages_de_DE.properties: ASCII text
>>>> messages_es.properties: ASCII text, with very long lines
>>>> messages_fr_FR.properties: ASCII text, with very long lines
>>>> messages_it_IT.properties: ASCII text, with very long lines
>>>> messages_ja.properties: ASCII text, with very long lines
>>>> messages_ko_KR.properties: ASCII text, with very long lines
>>>> messages_nb_NO.properties: ASCII text
>>>> messages.properties: ASCII text, with very long lines
>>>> messages_pt_BR.properties: ASCII text, with very long lines
>>>> messages_ru_RU.properties: ASCII text, with very long lines
>>>> messages_zh_CN.properties: ASCII text, with very long lines
>>>>
>>>> Milamber
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen<ru...@gmail.com>**
>>>>> wrote:
>>>>>
>>>>> Milamber, I made you a manager of the transifex project so you can help
>>>>>> fixing those issues.
>>>>>>
>>>>>> -sebastien
>>>>>>
>>>>>> On Apr 22, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>>
>>>>>>
>>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>>>>
>>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>>>>
>>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>>>>
>>>>>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>>>>>>
>>>>>>>>> This screenshots shows some characters with a incorrect encoding (try
>>>>>>>>>
>>>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>>>>>> encoding is
>>>>>> a UTF-8, I think)
>>>>>>
>>>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>>>>>>>> encoding charset in this files (ASCII with unicode). The transifex
>>>>>> data
>>>>>> isn't up-to-date.
>>>>>>
>>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>>>>>>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>>>> The last version of resources files is ASCII with unicode for *all
>>>>>>>> chars* in each file, and now transifex keep the unicode char (check
>>>>>> with FR
>>>>>> download for use)
>>>>>>
>>>>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>>>>
>>>>>>> The way the original workflow was:
>>>>>>>> -Upload new versions of the resources file in english
>>>>>>>> -Translators create a new language in transifex.
>>>>>>>> -Download new language resources file
>>>>>>>> -Fix encoding
>>>>>>>>
>>>>>>> For the fix encoding step, we can use this (unix and JDK) commands for
>>>>>>>
>>>>>> each language:
>>>>>>
>>>>>>> CODELANG=it_IT
>>>>>>>
>>>>>>> FILE_TRANSIFEX=for_use_**CloudStack_UI_**41xmessageproperties_${**CODELANG}.properties
>>>>>>
>>>>>>> FILE_RES=messages_${CODELANG}.**properties
>>>>>>>
>>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-**unicode
>>>>>>>
>>>>>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-**unicode | sort -f | uniq |
>>>>>>> sed
>>>>>>>
>>>>>> "s/'/\\\\\\\\\'/g">
>>>>>> /tmp/${FILE_RES}.ascii-with-**unicode_doublebackslashquote
>>>>>>
>>>>>>> # Define Apache Licence Header (one long line)
>>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>>>>>>
>>>>>> one\n# or more contributor license agreements. See the NOTICE file\n#
>>>>>> distributed with this work for additional information\n# regarding
>>>>>> copyright ownership. The ASF licenses this file\n# to you under the
>>>>>> Apache
>>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
>>>>>> except
>>>>>> in compliance\n# with the License. You may obtain a copy of the License
>>>>>> at\n#\n# http://www.apache.org/**licenses/LICENSE-2.0\n#\n#<http://www.apache.org/licenses/LICENSE-2.0%5Cn#%5Cn%23>Unless
>>>>>> required by applicable law or agreed to in writing,\n# software
>>>>>> distributed
>>>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
>>>>>> the License for the\n# specific language governing permissions and
>>>>>> limitations\n# under the License."
>>>>>>
>>>>>>> # Re-introduce the AL2 header
>>>>>>> echo -e "$AL2_STRING" | cat -
>>>>>>>
>>>>>> /tmp/${FILE_RES}.ascii-with-**unicode_doublebackslashquote>
>>>>>> ./FOR_REPO_${FILE_RES}
>>>>>>
>>>>>>> So I never uploaded the language specific resource file to transifex.
>>>>>>> Won't we have a problem that they won't stay in sync with the en-US
>>>>>> resource file, if it gets changed ?
>>>>>>
>>>>>>> On upload, Transifex seems only get the matching key with source
>>>>>>>
>>>>>> language.
>>>>>>
>>>>>>> In any case I uploaded the ja-JP resource file and the result on
>>>>>>> transifex is less than optimal, check the unreviewed strings, there is
>>>>>> a
>>>>>> mix of encoding.
>>>>>>
>>>>>>> We needs to revert the native to ascii convert.
>>>>>>> We can use this steps for each language before uploading on transifex :
>>>>>>>
>>>>>>> CODELANG=ja
>>>>>>> FILE_RES=messages_${CODELANG}.**properties
>>>>>>>
>>>>>>> # Revert convert
>>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>>>>
>>>>>>> # Remove double backslashes before quote
>>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1> ${FILE_RES}.native
>>>>>>>
>>>>>>>
>>>>>>> I've tested this commandes for download/upload with French language,
>>>>>>> and
>>>>>>>
>>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>>>
>>>>>>> I can make one shell script to automate this, and put in a tools dir in
>>>>>>>
>>>>>> CS git repo.
>>>>>>
>>>>>>> Milamber
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Milamber
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The other languages are ok.
>>>>>>>>>>
>>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>>>>>>>>>> runseb@gmail.com
>>>>>>>>>>
>>>>>>>>> wrote:
>>>>>>>> Hi,
>>>>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>>>>
>>>>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>>>>>>>>>>
>>>>>>>>>> below are
>>>>>>> some screenshots:
>>>>>>>>>>> The runbook:
>>>>>>>>>>> http://awesomescreenshot.com/**0bd163zldd<http://awesomescreenshot.com/0bd163zldd>
>>>>>>>>>>>
>>>>>>>>>>> The UI:
>>>>>>>>>>> http://awesomescreenshot.com/**089163zva2<http://awesomescreenshot.com/089163zva2>
>>>>>>>>>>>
>>>>>>>>>>> The entire docs set:
>>>>>>>>>>> http://awesomescreenshot.com/**01c163zq63<http://awesomescreenshot.com/01c163zq63>
>>>>>>>>>>>
>>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>>>>>>>>>>>
>>>>>>>>>> the UI
>>>>>>> translations.
>>>>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>>
>>>>>>>>>>> -Sebastien
>>>>>>>>>>>
>>>>>>>>>>
>>>>
>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 25/04/2013 08:05, Gavin Lee a ecrit :
> Done for zh_CN translation on transifex for master branch.
Thanks. I just update the master branch.
>
> For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect and
> resource files are not maintained by community.
Yes, the encoding's translation are incorrect.
I don't know where we can find the original 2.2 resource file to fix it.
But I don't if we must maintain the version 2.2...
Milamber
>
>
> On Wed, Apr 24, 2013 at 10:06 PM, Milamber<mi...@apache.org> wrote:
>
>>
>> Le 24/04/2013 10:44, Milamber a ecrit :
>>
>>
>>> Le 23/04/2013 13:50, Gavin Lee a ecrit :
>>>
>>>> Following Milamber's guide , below process I used for
>>>> 4.1.xmessage.properties on zh_CN:
>>>> 1. git pull for the latest messages_zh_CN.properties
>>>> 2. native2ascii -reverse messages_zh_CN.properties
>>>> /tmp/zh_CN.properties.native -encoding utf8
>>>>
>>> -encoding utf8<=== not necessary (on my machine)
>>
>>
>> 3. copy to the CloudStack_UI transifex project:
>>>> cp/tmp/zh_CN.properties.native /
>>>> txprj/acsui/translations/**CloudStack_UI.**41xmessageproperties
>>>> 4. tx push -l zh_CN -r CloudStack_UI.**41xmessageproperties -t
>>>> 5. Do translation on transifex, there are some untranslated items when
>>>> syncing with en.properties
>>>> 6. tx pull -a
>>>>
>>>>
>>>> Then convert to ascii with unicode, the i18nedit tools throws exception,
>>>> I
>>>> tried native2ascii command as below and UI display correctly:
>>>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>>>
>>>> Are the whole processes above correct or not?
>>>>
>>> Yes the process is correct, but currently on master branch the
>>> messages_zh_CN.properties is not converting into a ASCII with unicode
>>> unlike the 4.1 branch.
>>> I will fix this for all messages_xx.properties on master branch today
>>> (tonight) (FRench is already convert)
>>>
>> I just have made the fix for chinese (zh_CN) resource file on master
>> branch. Now it's a ascii with unicode file and the process can execute
>> manually with transifex.
>> I made too a upload on transifex (with converting into native charset) for
>> fix all sentences which have been corrupts with a previous upload (perhaps
>> your upload I think)
>>
>>
>> Currently, missing 33 translations for master (4.2) resource file zn_CN on
>> transifex.
>>
>> Milamber
>>
>>
>>
>>> === (on master branch) ===
>>>
>>> cloudstack-dev/client/WEB-INF/**classes/resources$ file *
>>> messages_fr_FR.properties: ASCII text, with very long lines
>>> messages_ja.properties: UTF-8 Unicode text, with very long lines
>>> messages_ko_KR.properties: UTF-8 Unicode text, with very long lines
>>> messages.properties: ASCII text, with very long lines
>>> messages_pt_BR.properties: ISO-8859 text, with very long lines
>>> messages_ru_RU.properties: UTF-8 Unicode text, with very long lines, with
>>> CRLF line terminators
>>> messages_zh_CN.properties: UTF-8 Unicode text, with very long lines, with
>>> CRLF, LF line terminators
>>>
>>> === (on 4.1 branch) ===
>>> cloudstack-dev/client/WEB-INF/**classes/resources$ file *
>>> messages_ca.properties: ASCII text, with very long lines
>>> messages_de_DE.properties: ASCII text
>>> messages_es.properties: ASCII text, with very long lines
>>> messages_fr_FR.properties: ASCII text, with very long lines
>>> messages_it_IT.properties: ASCII text, with very long lines
>>> messages_ja.properties: ASCII text, with very long lines
>>> messages_ko_KR.properties: ASCII text, with very long lines
>>> messages_nb_NO.properties: ASCII text
>>> messages.properties: ASCII text, with very long lines
>>> messages_pt_BR.properties: ASCII text, with very long lines
>>> messages_ru_RU.properties: ASCII text, with very long lines
>>> messages_zh_CN.properties: ASCII text, with very long lines
>>>
>>> Milamber
>>>
>>>
>>>
>>>>
>>>>
>>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen<ru...@gmail.com>**
>>>> wrote:
>>>>
>>>> Milamber, I made you a manager of the transifex project so you can help
>>>>> fixing those issues.
>>>>>
>>>>> -sebastien
>>>>>
>>>>> On Apr 22, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>
>>>>>
>>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>>>
>>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>>>
>>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>>>
>>>>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>>>>>
>>>>>>>> This screenshots shows some characters with a incorrect encoding (try
>>>>>>>>
>>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>>>>> encoding is
>>>>> a UTF-8, I think)
>>>>>
>>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>>>>>>> encoding charset in this files (ASCII with unicode). The transifex
>>>>> data
>>>>> isn't up-to-date.
>>>>>
>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>>>>>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>>> The last version of resources files is ASCII with unicode for *all
>>>>>>> chars* in each file, and now transifex keep the unicode char (check
>>>>> with FR
>>>>> download for use)
>>>>>
>>>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>>>
>>>>>> The way the original workflow was:
>>>>>>> -Upload new versions of the resources file in english
>>>>>>> -Translators create a new language in transifex.
>>>>>>> -Download new language resources file
>>>>>>> -Fix encoding
>>>>>>>
>>>>>> For the fix encoding step, we can use this (unix and JDK) commands for
>>>>>>
>>>>> each language:
>>>>>
>>>>>> CODELANG=it_IT
>>>>>>
>>>>>> FILE_TRANSIFEX=for_use_**CloudStack_UI_**41xmessageproperties_${**CODELANG}.properties
>>>>>
>>>>>> FILE_RES=messages_${CODELANG}.**properties
>>>>>>
>>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-**unicode
>>>>>>
>>>>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-**unicode | sort -f | uniq |
>>>>>> sed
>>>>>>
>>>>> "s/'/\\\\\\\\\'/g">
>>>>> /tmp/${FILE_RES}.ascii-with-**unicode_doublebackslashquote
>>>>>
>>>>>> # Define Apache Licence Header (one long line)
>>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>>>>>
>>>>> one\n# or more contributor license agreements. See the NOTICE file\n#
>>>>> distributed with this work for additional information\n# regarding
>>>>> copyright ownership. The ASF licenses this file\n# to you under the
>>>>> Apache
>>>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
>>>>> except
>>>>> in compliance\n# with the License. You may obtain a copy of the License
>>>>> at\n#\n# http://www.apache.org/**licenses/LICENSE-2.0\n#\n#<http://www.apache.org/licenses/LICENSE-2.0%5Cn#%5Cn%23>Unless
>>>>> required by applicable law or agreed to in writing,\n# software
>>>>> distributed
>>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
>>>>> the License for the\n# specific language governing permissions and
>>>>> limitations\n# under the License."
>>>>>
>>>>>> # Re-introduce the AL2 header
>>>>>> echo -e "$AL2_STRING" | cat -
>>>>>>
>>>>> /tmp/${FILE_RES}.ascii-with-**unicode_doublebackslashquote>
>>>>> ./FOR_REPO_${FILE_RES}
>>>>>
>>>>>> So I never uploaded the language specific resource file to transifex.
>>>>>> Won't we have a problem that they won't stay in sync with the en-US
>>>>> resource file, if it gets changed ?
>>>>>
>>>>>> On upload, Transifex seems only get the matching key with source
>>>>>>
>>>>> language.
>>>>>
>>>>>> In any case I uploaded the ja-JP resource file and the result on
>>>>>> transifex is less than optimal, check the unreviewed strings, there is
>>>>> a
>>>>> mix of encoding.
>>>>>
>>>>>> We needs to revert the native to ascii convert.
>>>>>> We can use this steps for each language before uploading on transifex :
>>>>>>
>>>>>> CODELANG=ja
>>>>>> FILE_RES=messages_${CODELANG}.**properties
>>>>>>
>>>>>> # Revert convert
>>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>>>
>>>>>> # Remove double backslashes before quote
>>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1> ${FILE_RES}.native
>>>>>>
>>>>>>
>>>>>> I've tested this commandes for download/upload with French language,
>>>>>> and
>>>>>>
>>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>>
>>>>>> I can make one shell script to automate this, and put in a tools dir in
>>>>>>
>>>>> CS git repo.
>>>>>
>>>>>> Milamber
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Milamber
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The other languages are ok.
>>>>>>>>>
>>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>>>>>>>>> runseb@gmail.com
>>>>>>>>>
>>>>>>>> wrote:
>>>>>>> Hi,
>>>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>>>
>>>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>>>>>>>>>
>>>>>>>>> below are
>>>>>> some screenshots:
>>>>>>>>>> The runbook:
>>>>>>>>>> http://awesomescreenshot.com/**0bd163zldd<http://awesomescreenshot.com/0bd163zldd>
>>>>>>>>>>
>>>>>>>>>> The UI:
>>>>>>>>>> http://awesomescreenshot.com/**089163zva2<http://awesomescreenshot.com/089163zva2>
>>>>>>>>>>
>>>>>>>>>> The entire docs set:
>>>>>>>>>> http://awesomescreenshot.com/**01c163zq63<http://awesomescreenshot.com/01c163zq63>
>>>>>>>>>>
>>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>>>>>>>>>>
>>>>>>>>> the UI
>>>>>> translations.
>>>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> -Sebastien
>>>>>>>>>>
>>>>>>>>>
>>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Gavin Lee <ga...@gmail.com>.
Done for zh_CN translation on transifex for master branch.
For 2.2.xmessages for zh_CN, and also for ja, the encoding is incorrect and
resource files are not maintained by community.
On Wed, Apr 24, 2013 at 10:06 PM, Milamber <mi...@apache.org> wrote:
>
>
> Le 24/04/2013 10:44, Milamber a ecrit :
>
>
>>
>> Le 23/04/2013 13:50, Gavin Lee a ecrit :
>>
>>> Following Milamber's guide , below process I used for
>>> 4.1.xmessage.properties on zh_CN:
>>> 1. git pull for the latest messages_zh_CN.properties
>>> 2. native2ascii -reverse messages_zh_CN.properties
>>> /tmp/zh_CN.properties.native -encoding utf8
>>>
>> -encoding utf8 <=== not necessary (on my machine)
>
>
>
> 3. copy to the CloudStack_UI transifex project:
>>> cp/tmp/zh_CN.properties.native /
>>> txprj/acsui/translations/**CloudStack_UI.**41xmessageproperties
>>> 4. tx push -l zh_CN -r CloudStack_UI.**41xmessageproperties -t
>>> 5. Do translation on transifex, there are some untranslated items when
>>> syncing with en.properties
>>> 6. tx pull -a
>>>
>>>
>>> Then convert to ascii with unicode, the i18nedit tools throws exception,
>>> I
>>> tried native2ascii command as below and UI display correctly:
>>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>>
>>> Are the whole processes above correct or not?
>>>
>>
>> Yes the process is correct, but currently on master branch the
>> messages_zh_CN.properties is not converting into a ASCII with unicode
>> unlike the 4.1 branch.
>> I will fix this for all messages_xx.properties on master branch today
>> (tonight) (FRench is already convert)
>>
>
> I just have made the fix for chinese (zh_CN) resource file on master
> branch. Now it's a ascii with unicode file and the process can execute
> manually with transifex.
> I made too a upload on transifex (with converting into native charset) for
> fix all sentences which have been corrupts with a previous upload (perhaps
> your upload I think)
>
>
> Currently, missing 33 translations for master (4.2) resource file zn_CN on
> transifex.
>
> Milamber
>
>
>
>> === (on master branch) ===
>>
>> cloudstack-dev/client/WEB-INF/**classes/resources$ file *
>> messages_fr_FR.properties: ASCII text, with very long lines
>> messages_ja.properties: UTF-8 Unicode text, with very long lines
>> messages_ko_KR.properties: UTF-8 Unicode text, with very long lines
>> messages.properties: ASCII text, with very long lines
>> messages_pt_BR.properties: ISO-8859 text, with very long lines
>> messages_ru_RU.properties: UTF-8 Unicode text, with very long lines, with
>> CRLF line terminators
>> messages_zh_CN.properties: UTF-8 Unicode text, with very long lines, with
>> CRLF, LF line terminators
>>
>> === (on 4.1 branch) ===
>> cloudstack-dev/client/WEB-INF/**classes/resources$ file *
>> messages_ca.properties: ASCII text, with very long lines
>> messages_de_DE.properties: ASCII text
>> messages_es.properties: ASCII text, with very long lines
>> messages_fr_FR.properties: ASCII text, with very long lines
>> messages_it_IT.properties: ASCII text, with very long lines
>> messages_ja.properties: ASCII text, with very long lines
>> messages_ko_KR.properties: ASCII text, with very long lines
>> messages_nb_NO.properties: ASCII text
>> messages.properties: ASCII text, with very long lines
>> messages_pt_BR.properties: ASCII text, with very long lines
>> messages_ru_RU.properties: ASCII text, with very long lines
>> messages_zh_CN.properties: ASCII text, with very long lines
>>
>> Milamber
>>
>>
>>
>>>
>>>
>>>
>>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen<ru...@gmail.com>**
>>> wrote:
>>>
>>> Milamber, I made you a manager of the transifex project so you can help
>>>> fixing those issues.
>>>>
>>>> -sebastien
>>>>
>>>> On Apr 22, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>
>>>>
>>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>>
>>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>>
>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>>
>>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>>
>>>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>>>>
>>>>>>> This screenshots shows some characters with a incorrect encoding (try
>>>>>>>
>>>>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>>>> encoding is
>>>> a UTF-8, I think)
>>>>
>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>>>>>>>
>>>>>> encoding charset in this files (ASCII with unicode). The transifex
>>>> data
>>>> isn't up-to-date.
>>>>
>>>>> Sebgoa, I think we must upload the last version of this (all)
>>>>>>>
>>>>>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>
>>>>> The last version of resources files is ASCII with unicode for *all
>>>>>>>
>>>>>> chars* in each file, and now transifex keep the unicode char (check
>>>> with FR
>>>> download for use)
>>>>
>>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>>
>>>>> The way the original workflow was:
>>>>>> -Upload new versions of the resources file in english
>>>>>> -Translators create a new language in transifex.
>>>>>> -Download new language resources file
>>>>>> -Fix encoding
>>>>>>
>>>>> For the fix encoding step, we can use this (unix and JDK) commands for
>>>>>
>>>> each language:
>>>>
>>>>> CODELANG=it_IT
>>>>>
>>>>> FILE_TRANSIFEX=for_use_**CloudStack_UI_**41xmessageproperties_${**CODELANG}.properties
>>>>
>>>>
>>>>> FILE_RES=messages_${CODELANG}.**properties
>>>>>
>>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-**unicode
>>>>>
>>>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-**unicode | sort -f | uniq |
>>>>> sed
>>>>>
>>>> "s/'/\\\\\\\\\'/g">
>>>> /tmp/${FILE_RES}.ascii-with-**unicode_doublebackslashquote
>>>>
>>>>> # Define Apache Licence Header (one long line)
>>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>>>>
>>>> one\n# or more contributor license agreements. See the NOTICE file\n#
>>>> distributed with this work for additional information\n# regarding
>>>> copyright ownership. The ASF licenses this file\n# to you under the
>>>> Apache
>>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
>>>> except
>>>> in compliance\n# with the License. You may obtain a copy of the License
>>>> at\n#\n# http://www.apache.org/**licenses/LICENSE-2.0\n#\n#<http://www.apache.org/licenses/LICENSE-2.0%5Cn#%5Cn%23>Unless
>>>> required by applicable law or agreed to in writing,\n# software
>>>> distributed
>>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
>>>> the License for the\n# specific language governing permissions and
>>>> limitations\n# under the License."
>>>>
>>>>> # Re-introduce the AL2 header
>>>>> echo -e "$AL2_STRING" | cat -
>>>>>
>>>> /tmp/${FILE_RES}.ascii-with-**unicode_doublebackslashquote>
>>>> ./FOR_REPO_${FILE_RES}
>>>>
>>>>>
>>>>> So I never uploaded the language specific resource file to transifex.
>>>>>>
>>>>> Won't we have a problem that they won't stay in sync with the en-US
>>>> resource file, if it gets changed ?
>>>>
>>>>> On upload, Transifex seems only get the matching key with source
>>>>>
>>>> language.
>>>>
>>>>> In any case I uploaded the ja-JP resource file and the result on
>>>>>>
>>>>> transifex is less than optimal, check the unreviewed strings, there is
>>>> a
>>>> mix of encoding.
>>>>
>>>>> We needs to revert the native to ascii convert.
>>>>> We can use this steps for each language before uploading on transifex :
>>>>>
>>>>> CODELANG=ja
>>>>> FILE_RES=messages_${CODELANG}.**properties
>>>>>
>>>>> # Revert convert
>>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>>
>>>>> # Remove double backslashes before quote
>>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1> ${FILE_RES}.native
>>>>>
>>>>>
>>>>> I've tested this commandes for download/upload with French language,
>>>>> and
>>>>>
>>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>
>>>>>
>>>>> I can make one shell script to automate this, and put in a tools dir in
>>>>>
>>>> CS git repo.
>>>>
>>>>> Milamber
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Milamber
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The other languages are ok.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<
>>>>>>>> runseb@gmail.com
>>>>>>>>
>>>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>>
>>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>>>>>>>>
>>>>>>>> below are
>>>>
>>>>> some screenshots:
>>>>>>>>>
>>>>>>>>> The runbook:
>>>>>>>>> http://awesomescreenshot.com/**0bd163zldd<http://awesomescreenshot.com/0bd163zldd>
>>>>>>>>>
>>>>>>>>> The UI:
>>>>>>>>> http://awesomescreenshot.com/**089163zva2<http://awesomescreenshot.com/089163zva2>
>>>>>>>>>
>>>>>>>>> The entire docs set:
>>>>>>>>> http://awesomescreenshot.com/**01c163zq63<http://awesomescreenshot.com/01c163zq63>
>>>>>>>>>
>>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>>>>>>>>>
>>>>>>>> the UI
>>>>
>>>>> translations.
>>>>>>>>>
>>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> -Sebastien
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>
>>
>>
>
--
Gavin
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 24/04/2013 10:44, Milamber a ecrit :
>
>
> Le 23/04/2013 13:50, Gavin Lee a ecrit :
>> Following Milamber's guide , below process I used for
>> 4.1.xmessage.properties on zh_CN:
>> 1. git pull for the latest messages_zh_CN.properties
>> 2. native2ascii -reverse messages_zh_CN.properties
>> /tmp/zh_CN.properties.native -encoding utf8
-encoding utf8 <=== not necessary (on my machine)
>> 3. copy to the CloudStack_UI transifex project:
>> cp/tmp/zh_CN.properties.native /
>> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
>> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
>> 5. Do translation on transifex, there are some untranslated items when
>> syncing with en.properties
>> 6. tx pull -a
>>
>>
>> Then convert to ascii with unicode, the i18nedit tools throws
>> exception, I
>> tried native2ascii command as below and UI display correctly:
>> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>>
>> Are the whole processes above correct or not?
>
> Yes the process is correct, but currently on master branch the
> messages_zh_CN.properties is not converting into a ASCII with unicode
> unlike the 4.1 branch.
> I will fix this for all messages_xx.properties on master branch today
> (tonight) (FRench is already convert)
I just have made the fix for chinese (zh_CN) resource file on master
branch. Now it's a ascii with unicode file and the process can execute
manually with transifex.
I made too a upload on transifex (with converting into native charset)
for fix all sentences which have been corrupts with a previous upload
(perhaps your upload I think)
Currently, missing 33 translations for master (4.2) resource file zn_CN
on transifex.
Milamber
>
> === (on master branch) ===
>
> cloudstack-dev/client/WEB-INF/classes/resources$ file *
> messages_fr_FR.properties: ASCII text, with very long lines
> messages_ja.properties: UTF-8 Unicode text, with very long lines
> messages_ko_KR.properties: UTF-8 Unicode text, with very long lines
> messages.properties: ASCII text, with very long lines
> messages_pt_BR.properties: ISO-8859 text, with very long lines
> messages_ru_RU.properties: UTF-8 Unicode text, with very long lines,
> with CRLF line terminators
> messages_zh_CN.properties: UTF-8 Unicode text, with very long lines,
> with CRLF, LF line terminators
>
> === (on 4.1 branch) ===
> cloudstack-dev/client/WEB-INF/classes/resources$ file *
> messages_ca.properties: ASCII text, with very long lines
> messages_de_DE.properties: ASCII text
> messages_es.properties: ASCII text, with very long lines
> messages_fr_FR.properties: ASCII text, with very long lines
> messages_it_IT.properties: ASCII text, with very long lines
> messages_ja.properties: ASCII text, with very long lines
> messages_ko_KR.properties: ASCII text, with very long lines
> messages_nb_NO.properties: ASCII text
> messages.properties: ASCII text, with very long lines
> messages_pt_BR.properties: ASCII text, with very long lines
> messages_ru_RU.properties: ASCII text, with very long lines
> messages_zh_CN.properties: ASCII text, with very long lines
>
> Milamber
>
>
>>
>>
>>
>>
>> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien
>> Goasguen<ru...@gmail.com>wrote:
>>
>>> Milamber, I made you a manager of the transifex project so you can help
>>> fixing those issues.
>>>
>>> -sebastien
>>>
>>> On Apr 22, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>
>>>>
>>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>>
>>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>>
>>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>>> This screenshots shows some characters with a incorrect encoding
>>>>>> (try
>>> to display a char as a ISO-8859-1 (or japanese charset) but the
>>> encoding is
>>> a UTF-8, I think)
>>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>>> encoding charset in this files (ASCII with unicode). The transifex data
>>> isn't up-to-date.
>>>>>> Sebgoa, I think we must upload the last version of this (all)
>>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>>> The last version of resources files is ASCII with unicode for *all
>>> chars* in each file, and now transifex keep the unicode char (check
>>> with FR
>>> download for use)
>>>> Mistake: transifex don't support uploaded unicode chars.
>>>>
>>>>> The way the original workflow was:
>>>>> -Upload new versions of the resources file in english
>>>>> -Translators create a new language in transifex.
>>>>> -Download new language resources file
>>>>> -Fix encoding
>>>> For the fix encoding step, we can use this (unix and JDK) commands for
>>> each language:
>>>> CODELANG=it_IT
>>>>
>>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>>
>>>> FILE_RES=messages_${CODELANG}.properties
>>>>
>>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>>
>>>> # sort key, add a double-backslash before the quote char ( ' ==>
>>>> \\' )
>>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq |
>>>> sed
>>> "s/'/\\\\\\\\\'/g">
>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>>> # Define Apache Licence Header (one long line)
>>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>>> one\n# or more contributor license agreements. See the NOTICE file\n#
>>> distributed with this work for additional information\n# regarding
>>> copyright ownership. The ASF licenses this file\n# to you under the
>>> Apache
>>> License, Version 2.0 (the\n# \"License\"); you may not use this file
>>> except
>>> in compliance\n# with the License. You may obtain a copy of the
>>> License
>>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>>> required by applicable law or agreed to in writing,\n# software
>>> distributed
>>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.
>>> See
>>> the License for the\n# specific language governing permissions and
>>> limitations\n# under the License."
>>>> # Re-introduce the AL2 header
>>>> echo -e "$AL2_STRING" | cat -
>>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote>
>>> ./FOR_REPO_${FILE_RES}
>>>>
>>>>> So I never uploaded the language specific resource file to transifex.
>>> Won't we have a problem that they won't stay in sync with the en-US
>>> resource file, if it gets changed ?
>>>> On upload, Transifex seems only get the matching key with source
>>> language.
>>>>> In any case I uploaded the ja-JP resource file and the result on
>>> transifex is less than optimal, check the unreviewed strings, there
>>> is a
>>> mix of encoding.
>>>> We needs to revert the native to ascii convert.
>>>> We can use this steps for each language before uploading on
>>>> transifex :
>>>>
>>>> CODELANG=ja
>>>> FILE_RES=messages_${CODELANG}.properties
>>>>
>>>> # Revert convert
>>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>>
>>>> # Remove double backslashes before quote
>>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1> ${FILE_RES}.native
>>>>
>>>>
>>>> I've tested this commandes for download/upload with French
>>>> language, and
>>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>>
>>>> I can make one shell script to automate this, and put in a tools
>>>> dir in
>>> CS git repo.
>>>> Milamber
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>> Milamber
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> The other languages are ok.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien
>>>>>>> Goasguen<runseb@gmail.com
>>>> wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> There has been some terrific progress on the translations.
>>>>>>>>
>>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>>> below are
>>>>>>>> some screenshots:
>>>>>>>>
>>>>>>>> The runbook:
>>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>>
>>>>>>>> The UI:
>>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>>
>>>>>>>> The entire docs set:
>>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>>
>>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>>> the UI
>>>>>>>> translations.
>>>>>>>>
>>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>>> CloudStack a truly worldwide project.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> -Sebastien
>>>>>>>
>>>
>>
>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 23/04/2013 13:50, Gavin Lee a ecrit :
> Following Milamber's guide , below process I used for
> 4.1.xmessage.properties on zh_CN:
> 1. git pull for the latest messages_zh_CN.properties
> 2. native2ascii -reverse messages_zh_CN.properties
> /tmp/zh_CN.properties.native -encoding utf8
> 3. copy to the CloudStack_UI transifex project: cp/tmp/zh_CN.properties.native /
> txprj/acsui/translations/CloudStack_UI.41xmessageproperties
> 4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
> 5. Do translation on transifex, there are some untranslated items when
> syncing with en.properties
> 6. tx pull -a
>
>
> Then convert to ascii with unicode, the i18nedit tools throws exception, I
> tried native2ascii command as below and UI display correctly:
> native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
>
> Are the whole processes above correct or not?
Yes the process is correct, but currently on master branch the
messages_zh_CN.properties is not converting into a ASCII with unicode
unlike the 4.1 branch.
I will fix this for all messages_xx.properties on master branch today
(tonight) (FRench is already convert)
=== (on master branch) ===
cloudstack-dev/client/WEB-INF/classes/resources$ file *
messages_fr_FR.properties: ASCII text, with very long lines
messages_ja.properties: UTF-8 Unicode text, with very long lines
messages_ko_KR.properties: UTF-8 Unicode text, with very long lines
messages.properties: ASCII text, with very long lines
messages_pt_BR.properties: ISO-8859 text, with very long lines
messages_ru_RU.properties: UTF-8 Unicode text, with very long lines,
with CRLF line terminators
messages_zh_CN.properties: UTF-8 Unicode text, with very long lines,
with CRLF, LF line terminators
=== (on 4.1 branch) ===
cloudstack-dev/client/WEB-INF/classes/resources$ file *
messages_ca.properties: ASCII text, with very long lines
messages_de_DE.properties: ASCII text
messages_es.properties: ASCII text, with very long lines
messages_fr_FR.properties: ASCII text, with very long lines
messages_it_IT.properties: ASCII text, with very long lines
messages_ja.properties: ASCII text, with very long lines
messages_ko_KR.properties: ASCII text, with very long lines
messages_nb_NO.properties: ASCII text
messages.properties: ASCII text, with very long lines
messages_pt_BR.properties: ASCII text, with very long lines
messages_ru_RU.properties: ASCII text, with very long lines
messages_zh_CN.properties: ASCII text, with very long lines
Milamber
>
>
>
>
> On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen<ru...@gmail.com>wrote:
>
>> Milamber, I made you a manager of the transifex project so you can help
>> fixing those issues.
>>
>> -sebastien
>>
>> On Apr 22, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>
>>>
>>> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>>>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>>>
>>>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>>>> Yes, Traditional Chinese moving very quickly.
>>>>>> Hopefully, the other languages can have more contributors.
>>>>>>
>>>>>> For the UI part, I saw the characters are not recognizable (browser
>>>>>> encoding setting: auto detect& Unicode UTF-8):
>>>>>> ja: http://snag.gy/AVsbU.jpg
>>>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>>>> This screenshots shows some characters with a incorrect encoding (try
>> to display a char as a ISO-8859-1 (or japanese charset) but the encoding is
>> a UTF-8, I think)
>>>>> With Sebgoa, we have correct all UI ressource file to have only one
>> encoding charset in this files (ASCII with unicode). The transifex data
>> isn't up-to-date.
>>>>> Sebgoa, I think we must upload the last version of this (all)
>> resources files (except FR already done) from branch 4.1 to transifex.
>>>>> The last version of resources files is ASCII with unicode for *all
>> chars* in each file, and now transifex keep the unicode char (check with FR
>> download for use)
>>> Mistake: transifex don't support uploaded unicode chars.
>>>
>>>> The way the original workflow was:
>>>> -Upload new versions of the resources file in english
>>>> -Translators create a new language in transifex.
>>>> -Download new language resources file
>>>> -Fix encoding
>>> For the fix encoding step, we can use this (unix and JDK) commands for
>> each language:
>>> CODELANG=it_IT
>>>
>> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
>>> FILE_RES=messages_${CODELANG}.properties
>>>
>>> # Convert to ascii with unicode (native2ascii is a JDK tool)
>>> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>>>
>>> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
>>> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed
>> "s/'/\\\\\\\\\'/g">
>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>>> # Define Apache Licence Header (one long line)
>>> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
>> one\n# or more contributor license agreements. See the NOTICE file\n#
>> distributed with this work for additional information\n# regarding
>> copyright ownership. The ASF licenses this file\n# to you under the Apache
>> License, Version 2.0 (the\n# \"License\"); you may not use this file except
>> in compliance\n# with the License. You may obtain a copy of the License
>> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
>> required by applicable law or agreed to in writing,\n# software distributed
>> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
>> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
>> the License for the\n# specific language governing permissions and
>> limitations\n# under the License."
>>> # Re-introduce the AL2 header
>>> echo -e "$AL2_STRING" | cat -
>> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote>
>> ./FOR_REPO_${FILE_RES}
>>>
>>>> So I never uploaded the language specific resource file to transifex.
>> Won't we have a problem that they won't stay in sync with the en-US
>> resource file, if it gets changed ?
>>> On upload, Transifex seems only get the matching key with source
>> language.
>>>> In any case I uploaded the ja-JP resource file and the result on
>> transifex is less than optimal, check the unreviewed strings, there is a
>> mix of encoding.
>>> We needs to revert the native to ascii convert.
>>> We can use this steps for each language before uploading on transifex :
>>>
>>> CODELANG=ja
>>> FILE_RES=messages_${CODELANG}.properties
>>>
>>> # Revert convert
>>> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>>>
>>> # Remove double backslashes before quote
>>> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1> ${FILE_RES}.native
>>>
>>>
>>> I've tested this commandes for download/upload with French language, and
>> just for download with ko_KR, it_IT, ca, ja, pt_BR.
>>>
>>> I can make one shell script to automate this, and put in a tools dir in
>> CS git repo.
>>> Milamber
>>>
>>>
>>>
>>>
>>>
>>>>
>>>>> Milamber
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> The other languages are ok.
>>>>>>
>>>>>>
>>>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<runseb@gmail.com
>>> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> There has been some terrific progress on the translations.
>>>>>>>
>>>>>>> The easiest way to share it is to check the Transifex dashboard,
>> below are
>>>>>>> some screenshots:
>>>>>>>
>>>>>>> The runbook:
>>>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>>>
>>>>>>> The UI:
>>>>>>> http://awesomescreenshot.com/089163zva2
>>>>>>>
>>>>>>> The entire docs set:
>>>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>>>
>>>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
>> the UI
>>>>>>> translations.
>>>>>>>
>>>>>>> Keep getting the word out, forward to friends and let's all make
>>>>>>> CloudStack a truly worldwide project.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> -Sebastien
>>>>>>
>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Gavin Lee <ga...@gmail.com>.
Following Milamber's guide , below process I used for
4.1.xmessage.properties on zh_CN:
1. git pull for the latest messages_zh_CN.properties
2. native2ascii -reverse messages_zh_CN.properties
/tmp/zh_CN.properties.native -encoding utf8
3. copy to the CloudStack_UI transifex project: cp/tmp/zh_CN.properties.native /
txprj/acsui/translations/CloudStack_UI.41xmessageproperties
4. tx push -l zh_CN -r CloudStack_UI.41xmessageproperties -t
5. Do translation on transifex, there are some untranslated items when
syncing with en.properties
6. tx pull -a
Then convert to ascii with unicode, the i18nedit tools throws exception, I
tried native2ascii command as below and UI display correctly:
native2ascii -encoding UTF-8 zh_CN.properties messages_zh_CN.properties
Are the whole processes above correct or not?
On Tue, Apr 23, 2013 at 12:01 AM, Sebastien Goasguen <ru...@gmail.com>wrote:
> Milamber, I made you a manager of the transifex project so you can help
> fixing those issues.
>
> -sebastien
>
> On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
>
> >
> >
> > Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> >> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
> >>
> >>>
> >>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
> >>>> Yes, Traditional Chinese moving very quickly.
> >>>> Hopefully, the other languages can have more contributors.
> >>>>
> >>>> For the UI part, I saw the characters are not recognizable (browser
> >>>> encoding setting: auto detect& Unicode UTF-8):
> >>>> ja: http://snag.gy/AVsbU.jpg
> >>>> zh_CN: http://snag.gy/MxbBS.jpg
> >>> This screenshots shows some characters with a incorrect encoding (try
> to display a char as a ISO-8859-1 (or japanese charset) but the encoding is
> a UTF-8, I think)
> >>>
> >>> With Sebgoa, we have correct all UI ressource file to have only one
> encoding charset in this files (ASCII with unicode). The transifex data
> isn't up-to-date.
> >>>
> >>> Sebgoa, I think we must upload the last version of this (all)
> resources files (except FR already done) from branch 4.1 to transifex.
> >>> The last version of resources files is ASCII with unicode for *all
> chars* in each file, and now transifex keep the unicode char (check with FR
> download for use)
> >
> > Mistake: transifex don't support uploaded unicode chars.
> >
> >> The way the original workflow was:
> >> -Upload new versions of the resources file in english
> >> -Translators create a new language in transifex.
> >> -Download new language resources file
> >> -Fix encoding
> >
> > For the fix encoding step, we can use this (unix and JDK) commands for
> each language:
> >
> > CODELANG=it_IT
> >
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> > FILE_RES=messages_${CODELANG}.properties
> >
> > # Convert to ascii with unicode (native2ascii is a JDK tool)
> > native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
> >
> > # sort key, add a double-backslash before the quote char ( ' ==> \\' )
> > grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed
> "s/'/\\\\\\\\\'/g" >
> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> >
> > # Define Apache Licence Header (one long line)
> > AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding
> copyright ownership. The ASF licenses this file\n# to you under the Apache
> License, Version 2.0 (the\n# \"License\"); you may not use this file except
> in compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless
> required by applicable law or agreed to in writing,\n# software distributed
> under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT
> WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See
> the License for the\n# specific language governing permissions and
> limitations\n# under the License."
> >
> > # Re-introduce the AL2 header
> > echo -e "$AL2_STRING" | cat -
> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
> ./FOR_REPO_${FILE_RES}
> >
> >
> >>
> >> So I never uploaded the language specific resource file to transifex.
> Won't we have a problem that they won't stay in sync with the en-US
> resource file, if it gets changed ?
> >
> > On upload, Transifex seems only get the matching key with source
> language.
> >
> >>
> >> In any case I uploaded the ja-JP resource file and the result on
> transifex is less than optimal, check the unreviewed strings, there is a
> mix of encoding.
> >
> > We needs to revert the native to ascii convert.
> > We can use this steps for each language before uploading on transifex :
> >
> > CODELANG=ja
> > FILE_RES=messages_${CODELANG}.properties
> >
> > # Revert convert
> > native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> >
> > # Remove double backslashes before quote
> > sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
> >
> >
> > I've tested this commandes for download/upload with French language, and
> just for download with ko_KR, it_IT, ca, ja, pt_BR.
> >
> >
> > I can make one shell script to automate this, and put in a tools dir in
> CS git repo.
> >
> > Milamber
> >
> >
> >
> >
> >
> >>
> >>
> >>> Milamber
> >>>
> >>>
> >>>
> >>>
> >>>> The other languages are ok.
> >>>>
> >>>>
> >>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<runseb@gmail.com
> >wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> There has been some terrific progress on the translations.
> >>>>>
> >>>>> The easiest way to share it is to check the Transifex dashboard,
> below are
> >>>>> some screenshots:
> >>>>>
> >>>>> The runbook:
> >>>>> http://awesomescreenshot.com/0bd163zldd
> >>>>>
> >>>>> The UI:
> >>>>> http://awesomescreenshot.com/089163zva2
> >>>>>
> >>>>> The entire docs set:
> >>>>> http://awesomescreenshot.com/01c163zq63
> >>>>>
> >>>>> Since 4.1 is not out yet, there is time to finish those last 3% on
> the UI
> >>>>> translations.
> >>>>>
> >>>>> Keep getting the word out, forward to friends and let's all make
> >>>>> CloudStack a truly worldwide project.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> -Sebastien
> >>>>
> >>>>
> >>
> >
>
>
--
Gavin
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
Milamber, I made you a manager of the transifex project so you can help fixing those issues.
-sebastien
On Apr 22, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
>
>
> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>>
>>>
>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>>> Yes, Traditional Chinese moving very quickly.
>>>> Hopefully, the other languages can have more contributors.
>>>>
>>>> For the UI part, I saw the characters are not recognizable (browser
>>>> encoding setting: auto detect& Unicode UTF-8):
>>>> ja: http://snag.gy/AVsbU.jpg
>>>> zh_CN: http://snag.gy/MxbBS.jpg
>>> This screenshots shows some characters with a incorrect encoding (try to display a char as a ISO-8859-1 (or japanese charset) but the encoding is a UTF-8, I think)
>>>
>>> With Sebgoa, we have correct all UI ressource file to have only one encoding charset in this files (ASCII with unicode). The transifex data isn't up-to-date.
>>>
>>> Sebgoa, I think we must upload the last version of this (all) resources files (except FR already done) from branch 4.1 to transifex.
>>> The last version of resources files is ASCII with unicode for *all chars* in each file, and now transifex keep the unicode char (check with FR download for use)
>
> Mistake: transifex don't support uploaded unicode chars.
>
>> The way the original workflow was:
>> -Upload new versions of the resources file in english
>> -Translators create a new language in transifex.
>> -Download new language resources file
>> -Fix encoding
>
> For the fix encoding step, we can use this (unix and JDK) commands for each language:
>
> CODELANG=it_IT
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> FILE_RES=messages_${CODELANG}.properties
>
> # Convert to ascii with unicode (native2ascii is a JDK tool)
> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
>
> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed "s/'/\\\\\\\\\'/g" > /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
>
> # Define Apache Licence Header (one long line)
> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under one\n# or more contributor license agreements. See the NOTICE file\n# distributed with this work for additional information\n# regarding copyright ownership. The ASF licenses this file\n# to you under the Apache License, Version 2.0 (the\n# \"License\"); you may not use this file except in compliance\n# with the License. You may obtain a copy of the License at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by applicable law or agreed to in writing,\n# software distributed under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied. See the License for the\n# specific language governing permissions and limitations\n# under the License."
>
> # Re-introduce the AL2 header
> echo -e "$AL2_STRING" | cat - /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote > ./FOR_REPO_${FILE_RES}
>
>
>>
>> So I never uploaded the language specific resource file to transifex. Won't we have a problem that they won't stay in sync with the en-US resource file, if it gets changed ?
>
> On upload, Transifex seems only get the matching key with source language.
>
>>
>> In any case I uploaded the ja-JP resource file and the result on transifex is less than optimal, check the unreviewed strings, there is a mix of encoding.
>
> We needs to revert the native to ascii convert.
> We can use this steps for each language before uploading on transifex :
>
> CODELANG=ja
> FILE_RES=messages_${CODELANG}.properties
>
> # Revert convert
> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
>
> # Remove double backslashes before quote
> sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
>
>
> I've tested this commandes for download/upload with French language, and just for download with ko_KR, it_IT, ca, ja, pt_BR.
>
>
> I can make one shell script to automate this, and put in a tools dir in CS git repo.
>
> Milamber
>
>
>
>
>
>>
>>
>>> Milamber
>>>
>>>
>>>
>>>
>>>> The other languages are ok.
>>>>
>>>>
>>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<ru...@gmail.com>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> There has been some terrific progress on the translations.
>>>>>
>>>>> The easiest way to share it is to check the Transifex dashboard, below are
>>>>> some screenshots:
>>>>>
>>>>> The runbook:
>>>>> http://awesomescreenshot.com/0bd163zldd
>>>>>
>>>>> The UI:
>>>>> http://awesomescreenshot.com/089163zva2
>>>>>
>>>>> The entire docs set:
>>>>> http://awesomescreenshot.com/01c163zq63
>>>>>
>>>>> Since 4.1 is not out yet, there is time to finish those last 3% on the UI
>>>>> translations.
>>>>>
>>>>> Keep getting the word out, forward to friends and let's all make
>>>>> CloudStack a truly worldwide project.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> -Sebastien
>>>>
>>>>
>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
> On Apr 16, 2013, at 11:10 AM, Milamber<mi...@apache.org> wrote:
>
>>
>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>>> Yes, Traditional Chinese moving very quickly.
>>> Hopefully, the other languages can have more contributors.
>>>
>>> For the UI part, I saw the characters are not recognizable (browser
>>> encoding setting: auto detect& Unicode UTF-8):
>>> ja: http://snag.gy/AVsbU.jpg
>>> zh_CN: http://snag.gy/MxbBS.jpg
>> This screenshots shows some characters with a incorrect encoding (try to display a char as a ISO-8859-1 (or japanese charset) but the encoding is a UTF-8, I think)
>>
>> With Sebgoa, we have correct all UI ressource file to have only one encoding charset in this files (ASCII with unicode). The transifex data isn't up-to-date.
>>
>> Sebgoa, I think we must upload the last version of this (all) resources files (except FR already done) from branch 4.1 to transifex.
>> The last version of resources files is ASCII with unicode for *all chars* in each file, and now transifex keep the unicode char (check with FR download for use)
Mistake: transifex don't support uploaded unicode chars.
> The way the original workflow was:
> -Upload new versions of the resources file in english
> -Translators create a new language in transifex.
> -Download new language resources file
> -Fix encoding
For the fix encoding step, we can use this (unix and JDK) commands for
each language:
CODELANG=it_IT
FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
FILE_RES=messages_${CODELANG}.properties
# Convert to ascii with unicode (native2ascii is a JDK tool)
native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
# sort key, add a double-backslash before the quote char ( ' ==> \\' )
grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed
"s/'/\\\\\\\\\'/g" >
/tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
# Define Apache Licence Header (one long line)
AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under
one\n# or more contributor license agreements. See the NOTICE file\n#
distributed with this work for additional information\n# regarding
copyright ownership. The ASF licenses this file\n# to you under the
Apache License, Version 2.0 (the\n# \"License\"); you may not use this
file except in compliance\n# with the License. You may obtain a copy of
the License at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n#
Unless required by applicable law or agreed to in writing,\n# software
distributed under the License is distributed on an\n# \"AS IS\" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or
implied. See the License for the\n# specific language governing
permissions and limitations\n# under the License."
# Re-introduce the AL2 header
echo -e "$AL2_STRING" | cat -
/tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote >
./FOR_REPO_${FILE_RES}
>
> So I never uploaded the language specific resource file to transifex. Won't we have a problem that they won't stay in sync with the en-US resource file, if it gets changed ?
On upload, Transifex seems only get the matching key with source language.
>
> In any case I uploaded the ja-JP resource file and the result on transifex is less than optimal, check the unreviewed strings, there is a mix of encoding.
We needs to revert the native to ascii convert.
We can use this steps for each language before uploading on transifex :
CODELANG=ja
FILE_RES=messages_${CODELANG}.properties
# Revert convert
native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
# Remove double backslashes before quote
sed "s/\\\\\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
I've tested this commandes for download/upload with French language, and
just for download with ko_KR, it_IT, ca, ja, pt_BR.
I can make one shell script to automate this, and put in a tools dir in
CS git repo.
Milamber
>
>
>> Milamber
>>
>>
>>
>>
>>> The other languages are ok.
>>>
>>>
>>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<ru...@gmail.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> There has been some terrific progress on the translations.
>>>>
>>>> The easiest way to share it is to check the Transifex dashboard, below are
>>>> some screenshots:
>>>>
>>>> The runbook:
>>>> http://awesomescreenshot.com/0bd163zldd
>>>>
>>>> The UI:
>>>> http://awesomescreenshot.com/089163zva2
>>>>
>>>> The entire docs set:
>>>> http://awesomescreenshot.com/01c163zq63
>>>>
>>>> Since 4.1 is not out yet, there is time to finish those last 3% on the UI
>>>> translations.
>>>>
>>>> Keep getting the word out, forward to friends and let's all make
>>>> CloudStack a truly worldwide project.
>>>>
>>>> Cheers,
>>>>
>>>> -Sebastien
>>>
>>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Apr 16, 2013, at 11:10 AM, Milamber <mi...@apache.org> wrote:
>
>
> Le 16/04/2013 13:41, Gavin Lee a ecrit :
>> Yes, Traditional Chinese moving very quickly.
>> Hopefully, the other languages can have more contributors.
>>
>> For the UI part, I saw the characters are not recognizable (browser
>> encoding setting: auto detect& Unicode UTF-8):
>> ja: http://snag.gy/AVsbU.jpg
>> zh_CN: http://snag.gy/MxbBS.jpg
> This screenshots shows some characters with a incorrect encoding (try to display a char as a ISO-8859-1 (or japanese charset) but the encoding is a UTF-8, I think)
>
> With Sebgoa, we have correct all UI ressource file to have only one encoding charset in this files (ASCII with unicode). The transifex data isn't up-to-date.
>
> Sebgoa, I think we must upload the last version of this (all) resources files (except FR already done) from branch 4.1 to transifex.
> The last version of resources files is ASCII with unicode for *all chars* in each file, and now transifex keep the unicode char (check with FR download for use)
The way the original workflow was:
-Upload new versions of the resources file in english
-Translators create a new language in transifex.
-Download new language resources file
-Fix encoding
So I never uploaded the language specific resource file to transifex. Won't we have a problem that they won't stay in sync with the en-US resource file, if it gets changed ?
In any case I uploaded the ja-JP resource file and the result on transifex is less than optimal, check the unreviewed strings, there is a mix of encoding.
>
> Milamber
>
>
>
>
>> The other languages are ok.
>>
>>
>> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<ru...@gmail.com>wrote:
>>
>>> Hi,
>>>
>>> There has been some terrific progress on the translations.
>>>
>>> The easiest way to share it is to check the Transifex dashboard, below are
>>> some screenshots:
>>>
>>> The runbook:
>>> http://awesomescreenshot.com/0bd163zldd
>>>
>>> The UI:
>>> http://awesomescreenshot.com/089163zva2
>>>
>>> The entire docs set:
>>> http://awesomescreenshot.com/01c163zq63
>>>
>>> Since 4.1 is not out yet, there is time to finish those last 3% on the UI
>>> translations.
>>>
>>> Keep getting the word out, forward to friends and let's all make
>>> CloudStack a truly worldwide project.
>>>
>>> Cheers,
>>>
>>> -Sebastien
>>
>>
>>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Milamber <mi...@apache.org>.
Le 16/04/2013 13:41, Gavin Lee a ecrit :
> Yes, Traditional Chinese moving very quickly.
> Hopefully, the other languages can have more contributors.
>
> For the UI part, I saw the characters are not recognizable (browser
> encoding setting: auto detect& Unicode UTF-8):
> ja: http://snag.gy/AVsbU.jpg
> zh_CN: http://snag.gy/MxbBS.jpg
This screenshots shows some characters with a incorrect encoding (try to
display a char as a ISO-8859-1 (or japanese charset) but the encoding is
a UTF-8, I think)
With Sebgoa, we have correct all UI ressource file to have only one
encoding charset in this files (ASCII with unicode). The transifex data
isn't up-to-date.
Sebgoa, I think we must upload the last version of this (all) resources
files (except FR already done) from branch 4.1 to transifex.
The last version of resources files is ASCII with unicode for *all
chars* in each file, and now transifex keep the unicode char (check with
FR download for use)
Milamber
> The other languages are ok.
>
>
> On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen<ru...@gmail.com>wrote:
>
>> Hi,
>>
>> There has been some terrific progress on the translations.
>>
>> The easiest way to share it is to check the Transifex dashboard, below are
>> some screenshots:
>>
>> The runbook:
>> http://awesomescreenshot.com/0bd163zldd
>>
>> The UI:
>> http://awesomescreenshot.com/089163zva2
>>
>> The entire docs set:
>> http://awesomescreenshot.com/01c163zq63
>>
>> Since 4.1 is not out yet, there is time to finish those last 3% on the UI
>> translations.
>>
>> Keep getting the word out, forward to friends and let's all make
>> CloudStack a truly worldwide project.
>>
>> Cheers,
>>
>> -Sebastien
>
>
>
Re: [DOCS][TRANSLATIONS] Upate
Posted by Gavin Lee <ga...@gmail.com>.
Yes, Traditional Chinese moving very quickly.
Hopefully, the other languages can have more contributors.
For the UI part, I saw the characters are not recognizable (browser
encoding setting: auto detect & Unicode UTF-8):
ja: http://snag.gy/AVsbU.jpg
zh_CN: http://snag.gy/MxbBS.jpg
The other languages are ok.
On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguen <ru...@gmail.com>wrote:
> Hi,
>
> There has been some terrific progress on the translations.
>
> The easiest way to share it is to check the Transifex dashboard, below are
> some screenshots:
>
> The runbook:
> http://awesomescreenshot.com/0bd163zldd
>
> The UI:
> http://awesomescreenshot.com/089163zva2
>
> The entire docs set:
> http://awesomescreenshot.com/01c163zq63
>
> Since 4.1 is not out yet, there is time to finish those last 3% on the UI
> translations.
>
> Keep getting the word out, forward to friends and let's all make
> CloudStack a truly worldwide project.
>
> Cheers,
>
> -Sebastien
--
Gavin