September 2013 - OpenStack-I18n - lists.openstack.org

Re: [Openstack-i18n] Fw: [OpenStack-doc] Add Korean fonts for 'coluddoc-maven-plugins'
by Ying Chun Guo 18 Mar '14

18 Mar '14

Hi, Sungjin Can you give the font file or the link to download the font file to David Cramer? He can add it to the plugin and cut a release. @ the whole team If you have font issue with the Maven plugin, please send your font file to David Cramer. @ David Will the Maven plugin become very big if it contains so many font files? Is it possible to use system font instead? Is it possible to configure which font to download when downloading the binary plugin files? Regards Ying Chun Guo (Daisy) David Cramer <david.cramer(a)rackspace.com> wrote on 2013/08/13 03:13:14: > David Cramer <david.cramer(a)rackspace.com> > 2013/08/13 03:13 > > To > > Ying Chun Guo/China/IBM@IBMCN, > > cc > > Subject > > Re: Fw: [Openstack-i18n] [OpenStack-doc] Add Korean fonts for > 'coluddoc-maven-plugins' > > Hi Daisy, > So I'm surprised that those steps would work. You'd really have to do > "mvn clean install" to make a changed version of the plugin available > for local builds (and also be sure that your project depends on the > version you just built). > > In the thread below, Sungjin Gang had a message to me offering to > provide a Korean font file. I think I'd replied saying that if I were > given the file , I could add it to the plugin. Is there an open source > font file available somewhere that I can download? If so, I'll add it > immediately and cut a release. > > For each language that requires a special font, we'll have to add the > font to the plugin for it to work. > > Regards, > David > > On 08/12/2013 11:46 AM, Ying Chun Guo wrote: > > Hi, David > > > > Sungjin Gang is a Korean translator. When he was trying to generate the > > translated Korean documents, he found the Korean characters cannot be > > displayed and #### was displayed instead of Korean font. > > > > After several tests, he tried follow steps and had Korean font work. > > > >> Edit 'clouddoc-maven-plugins'[1]. > >> Recompiling plugin. > >> Edit 'openstack-manuals/[docs-name]/pom.xml', plugin dir. > >> and exe 'mvn clean generate-sources'. > >> Create PDF[2]. > > > > As I remembered, there was the same problem to Chinese and Japanese > > characters, and now there was problem for Korean characters. I wonder if > > there are same problems to other languages. I'd like to check with you > > if you have any thoughts to resolve the root of this issue, other than > > using this tricky way. > > > > Thanks and regards > > Ying Chun Guo (Daisy) > > > > ----- Forwarded by Ying Chun Guo/China/IBM on 2013/08/13 00:39 ----- > > > > Sungjin Gang <gang.sungjin(a)gmail.com> wrote on 2013/08/10 15:04:57: > > > >> Sungjin Gang <gang.sungjin(a)gmail.com> > >> 2013/08/10 15:04 > >> > >> To > >> > >> Ying Chun Guo/China/IBM@IBMCN, > >> > >> cc > >> > >> openstack-i18n(a)lists.openstack.org > >> > >> Subject > >> > >> Re: [Openstack-i18n] [OpenStack-doc] Add Korean fonts for 'coluddoc- > >> maven-plugins' > >> > >> Hi, ~~~ > >> > >> :)) > >> > >> View Korean font!!!!! > >> :)) > >> > >> Edit 'clouddoc-maven-plugins'[1]. > >> > >> Recompiling plugin. > >> > >> Edit 'openstack-manuals/[docs-name]/pom.xml', plugin dir. > >> > >> and exe 'mvn clean generate-sources'. > >> > >> Create PDF[2]. > >> > >> Um.. hahahahahahaaaaaaa~ :)) > >> > >> But not think to do it. hahahahahahahaaaaaaaaaa :-( > >> > >> [image removed] > >> > >> [1]: https://github.com/ujuc/clouddocs-maven-plugin/commit/ > >> cb0743a14ece9e86cdcb190e778a9f38319b5b9a > >> [2]: http://os.ujuc.kr/openstack-manuals/generated/ko_KR/basic- > >> install/target/docbkx/webhelp/grizzly/basic-install/apt/openstack- > >> basic-install-apt-grizzly.pdf > >> > >> Thanks, > >> Sungjin. > >> > >> Jul 30, 2013, 5:34 PM, Ying Chun Guo <guoyingc(a)cn.ibm.com> $)C작성: > >> > >> Hi, > >> > >> It seems that I have met with this problem before, but I cannot > >> remember how I resolve it. It was a long time ago. > >> > >> @amotoki and KATO, have you met with this problem and how did you > > resolve it? > >> > >> Regards > >> Ying Chun Guo (Daisy) > >> > >> ----- Forwarded by Ying Chun Guo/China/IBM on 2013/07/30 16:32 ----- > >> > >> Sungjin Gang <gang.sungjin(a)gmail.com> wrote on 2013/07/21 23:01:33: > >> > >> > Sungjin Gang <gang.sungjin(a)gmail.com> > >> > 2013/07/21 23:01 > >> > > >> > To > >> > > >> > david.cramer(a)rackspace.com, > >> > > >> > cc > >> > > >> > Openstack-i18n <openstack-i18n(a)lists.openstack.org>, openstack- > >> > docs(a)lists.openstack.org > >> > > >> > Subject > >> > > >> > [Openstack-i18n] [OpenStack-doc] Add Korean fonts for 'coluddoc- > >> maven-plugins' > >> > > >> > Hi, David > >> > > >> > This is Sungjin Kang, a coordinator of OpenStack I18N Korean Team. > >> > Could you help me out on the following problem? > >> > > >> > When creating a korean document using maven, all korean characters > >> > are displayed as "#####". > >> > > >> > While I was looking for the possible solution, I found out that > >> > Korean font might need to be added in "clouddoc-maven-plugins" > > youmanages. > >> > > >> > If this is the case (adding korean font), I would like to add a > >> > korean font called "Nanum fonts[1]" > >> > > >> > [1] http://en.wikipedia.org/wiki/Nanum_font > >> > > >> > I can prepare for the actual font file. However, I don't know what I > >> > need to do to add korean font. > >> > > >> > Could you help me out on this? > >> > > >> > Thanks, > >> > > >> > Sungjin Gang_______________________________________________ > >> > Openstack-i18n mailing list > >> > Openstack-i18n(a)lists.openstack.org > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > >> _______________________________________________ > >> Openstack-i18n mailing list > >> Openstack-i18n(a)lists.openstack.org > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >

3 7

Status of OpenStack Operations Guide in Chinese & Japanese
by Tom Fifield 28 Nov '13

28 Nov '13

Hi, Just wondering what the current status of OpenStack Operations Guide in Chinese & Japanese is? Regards, Tom

2 4

Action item: Transifex statistics API
by Gabriel Wainer 07 Oct '13

07 Oct '13

Hi All, Unfortunately I won't be able to participate in the next meeting, due to timezone it will be 4 AM here. Anyway, from the last meeting, I have the following item: ACTION: gabrielcw to take a look at Transifex API to see if it's able to get the translators information. I searched the API docs and as Daisy and Katomo mentioned in the last meeting, there's the API to retrieve some information for projects, but not yet for translators work. http://help.transifex.com/features/api/#statistics So I asked their help desk about what we want, and happily they will soon be rolling out support for that: http://support.transifex.com/customer/portal/questions/1326867-translators-… In fact, by the answer it should be already available but is not. I will keep an eye on that, and let you know! Hope that helps, Regards, Gabriel.

2 3

No meeting next Thursday
by Ying Chun Guo 28 Sep '13

28 Sep '13

Hi, team I will start my vacation today and be back to office on Oct. 8th. So I'm going to cancel the meeting on Oct. 3th (next Thursday). We can discuss through email for any topics, like the Havana release, the log message I18n policy, the coming design summit, and etc. We will meet on Oct. 17th on 0000 UTC then. Hope to talk to you there. Regards Ying Chun Guo (Daisy)

1 0

Log messages translation
by Gabriel Wainer 28 Sep '13

28 Sep '13

I saw this in another post, so to avoid confusion I'll ask here. How can we know what are log messages and what aren't in the translation strings? I ended up translating all messages, even logs I believe. Sure that some technical words and var names should be copied but i think it's ok to translate logs. Any guidelines on that? Thanks, Gabriel Wainer

4 6

How to use partially completed languages for devstack horizon?
by Tom Fifield 28 Sep '13

28 Sep '13

Hi i18n, I'm potentially giving a dashboard demo in Moscow next week, and thought it would be cool if I could change the language settings to use our almost-complete Russian translation. Does anyone have some easy steps I can follow to download the PO file from transifex and then configure devstack to use it? Regards, Tom

3 9

String changes in master
by Łukasz Jernaś 27 Sep '13

27 Sep '13

Hi! I've noticed string changes in master introduced in commit 21eaa8fa58d635c62f531c66c6c831fe7fbcdbb6 I've created a bug https://bugs.launchpad.net/horizon/+bug/1229749 and posted a review request with updated strings: https://review.openstack.org/#/c/48056/ Someone please take a look at it. Regards, -- Łukasz [DeeJay1] Jernaś

3 4

Vote results - translation importing policy
by Ying Chun Guo 27 Sep '13

27 Sep '13

Hi, I got 13 answers for this vote. ( I'm very happy to see so many active people in this mailing list. That's great. ) Here is the result: 1. importing policy Vote results: 5a | 3b | 9c | 1d 2. Whether to keep the old translations in Horizon Vote results: 4a | 6b | 2c (language coordinator decided) So the final answer to these 2 questions are: 1. language coordinator decided 2. No @ Coordinators of completed translation teams: If you are NOT comfortable to import the translations of your language in Havanna RC1, please let us know. @ Coordinators of other translation teams: If you want to import your translations in RC1, please let us know. I see the translations of Spanish and Russian are very active. If you are not comfortable to import your translations in RC1, you still have chance to import them in RC2 and the final release. Please let us know your decision as soon as possible, so that Akihiro Motoki can start the importing. Thank you for your hard work! ---vote answers--- 1. importing policy c - language coordinator decided d - All b - 90% translated. a/c - 100% translated, or language coordinator decided (maybe not 100%) b - only if 90% translated is possible, otherwise A a/c - 100% translated, or language coordinator decided (maybe not 100%) c - language coordinator decided c - language co-ordinator decided a/b/c - but if around 95-100%, coordinator decided. c - Language coordinator decided a/c - 100% translated or coordinator decided (or active translator if no coordinator) a - I think 100 %translated should be our goal c - language coordinator decided 2. Whether to keep the old translations in Horizon b – No a - Older versions of translations if in the past had become part of any release should be kept. a - But 100% translated. If Long term support version, All keep. :) c - If no language coodinator b> No, else language coordinator decided a - c - If no language coordinator b> No, else language coordinator decided a - if no coordinator, else language coordinator decided b - b - b - "Yes" in general, but **NO** for Havana. b - b - No if there is such a technical reason as Akihiro mentioned. ------------ Regards Ying Chun Guo (Daisy) > Ying Chun Guo/China/IBM > 2013/09/25 17:03 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Call for vote: translation importing policy > > Hi, team > > We are just before the translation importing, and we haven't gotten > a consensus to the importing policy. > Let's do a vote then. > The vote will be opened for 24 hours. > I only open this vote to i18n mail list yet. > But I will publish the vote results to public mail list and ask for comments. > The result of this vote will be used for Havanna RC1. > If we got strong opposition from the public mail list, > we still have chance to change it in Havanna RC2 and Havanna offical release. > > Please let us know your opinion. > > ------------------------------------------------- > 1. Which importing policy do you choose? (the policy to be used to > import translations from Transifex to Horizon ) > > a> 100% translated > b> 50% translated, ( or you can specify another percentage number ) > c> language coordinator decided > d> All languages in Transifex > e> others ____________ > > 2. Whether to keep the old translations in Horizon? > (There are some old translation po/mo files in Horizon. > They are old version. Most of them are not completed. ) > > a> Yes > b> No > > Regards > Ying Chun Guo (Daisy)

3 3

Call for vote: translation importing policy
by Ying Chun Guo 25 Sep '13

25 Sep '13

Hi, team We are just before the translation importing, and we haven't gotten a consensus to the importing policy. Let's do a vote then. The vote will be opened for 24 hours. I only open this vote to i18n mail list yet. But I will publish the vote results to public mail list and ask for comments. The result of this vote will be used for Havanna RC1. If we got strong opposition from the public mail list, we still have chance to change it in Havanna RC2 and Havanna offical release. Please let us know your opinion. ------------------------------------------------- 1. Which importing policy do you choose? (the policy to be used to import translations from Transifex to Horizon ) a> 100% translated b> 50% translated, ( or you can specify another percentage number ) c> language coordinator decided d> All languages in Transifex e> others ____________ 2. Whether to keep the old translations in Horizon? (There are some old translation po/mo files in Horizon. They are old version. Most of them are not completed. ) a> Yes b> No Regards Ying Chun Guo (Daisy)

11 15

(no subject)
by Danilo Ingami 25 Sep '13

25 Sep '13

Sent from mobile

1 0