- OpenStack-I18n - lists.openstack.org

Persian translate
by کاربرخوب لینوکس 29 Apr '15

29 Apr '15

Salam Hello I am Contributing some project to translate to farsi such as debian , ... I like to start and Contribute open stack translation for persian users. Thanks

2 1

Decreasing size of PO files
by Andreas Jaeger 23 Apr '15

23 Apr '15

Our PO files contain information about location (filename and line numbers) as well as untranslated strings. Dolph suggested to me recently to import into projects only the *translated* strings and I did some investigation and implementation. I don't expect this to have any negative impact but wanted to inform you and ask for feedback. We will continue to push the full location information to transifex and leave it in the POT files that are stored in each repository. Thus if you download a file from transifex, you have all location information. During the import from transifex into the OpenStack git repositories, our scripts remove the location information as well as any untranslated strings thus reducing the files to import significantly. This also reduces the change of an import significantly since a line number change will not cause many location information to be updated. The gettext tools we use can cope fine with this smaller PO file since it contains everything that is needed - just nothing more ;) Also, it's easy to rebuild the full PO file from the date in the repository using the msgmerge command: msgmerge POT-FILE PO-FILE -o FULL-PO-FILE As a first step, I have made this change for documentation projects like openstack-manuals only: https://review.openstack.org/176313 If this works as expected, I plan to do it for other projects as well. Please review and tell me if you have any further ideas or if I overlooked something, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 5

Final call for Horizon translations for Kilo
by Akihiro Motoki 23 Apr '15

23 Apr '15

Hi all! Horizon RC1 was just shipped yesterday. This means we are now in the deep string freeze and no string changes are expected. I hope you all keep your translations up-to-date in time. I would like to share some important topics with you. TRANSIFEX RESOURCE: Liberty development cycle is now open. You will see resource names with Liberty. For Kilo translation, please translate the resources whose names have "Kilo". IMPORTANT DATE: The final translation import is planed on Apr 23. I talked with David, Horizon PTL and the above date works for Horizon team. I don't set the exact time of the deadline, but I will do the final import in the day of Apr 23 (UTC timezone). Please don't bother me on the deadline:-) IMPORT CRITERIA: I would like to set the criteria to import to 90% completion rate (as we discussed before), OR language coordinator request. Horizon now covers various new services and in some case translation rate does not work, so I would like to honor language coordinator decision. Daisy and the team, does it make sense? If not, please start a new thread to discuss this topic. Thanks, Akihiro

3 8

Draft Documents published, next steps with draft publishing and RST translation
by Andreas Jaeger 19 Apr '15

19 Apr '15

As part of the draft publishing spec [1], we now publish all draft documents to docs.openstack.org/drafts. To read or review, go to http://docs.openstack.org/draft/draft-index.html Translation team, as part of this, the draft-i18n-manuals.html page has been removed, the content is in draft-index.html now. Next steps are moving draft language guides also to /draft/ For this, let's merge [2], release openstack-doc-tools 0.25 and then I'll adjust and remove the script changes from [3] and [4]. The script changes in [3] and [4] are part of the openstack-doc-tools patch [2] and give you the chance to review the patches and scripts independently. Andreas [1] http://specs.openstack.org/openstack/docs-specs/specs/kilo/draft-publishing… [2] https://review.openstack.org/175190 [3] https://review.openstack.org/#/c/162424/ [4] https://review.openstack.org/#/c/175157/ -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Status of the RST Documentation Toolchain
by Tom Fifield 16 Apr '15

16 Apr '15

Hi, Andreas, Daisy, Motoki-san and myself have just had an impromptu hour-long discussion regarding the Status of the RST Documentation Toolchain, particularly its translation components. This meeting was spurred on by the email to the i18n mailing list announcing the pending removal of docbook user guides, and all present acknowledged the meeting would have been great if it had happened sooner :) This is the brief summary! 1. Everyone involved wants to make translators happy, and hopes that the process of moving to RST can deliver an improved toolchain 2. There has been inadequate communication between the documentation team and the i18n team regarding requirements and timelines during this process and we will strive to improve this 3. Previous statement that RST-based docs would not be published without agreement on the translation toolchain was acknowledged 4. Based on the user guide example, about 50% of existing translated strings (1943 vs 943) need to be re-translated with the current conversion process 5. Noone on the i18n team had yet the opportunity to assess the strings produced by the RST in a fuller guide and problems weren't picked up with initial version of guides in the playground folder 6. Daisy in particular hasn't been able to log in to transifex today to check the new user guide. We are currently using the standard Sphinx translation tools, though, there was some definite concern over the quality of the strings produced by the RST, including: 1. Strings that should have been trivially updated during conversion from docbook without human interaction needed (eg **string**\n) 2. Strings that are entirely markup (eg :ref:`Boot_instance_from_image_and_attach_non-bootable_volume`) 3. Strings that contain significant amounts of markup 4. Strings that contain markup characters that are unusual for translations, eg backticks, asterisks 5. Strings that contain markup where placeholders were previously used 6. ... this list is incomplete and comes only from what amotoki and fifieldt saw during the meeting - the broader i18n community has not yet been asked for feedback outside of Andreas' recent email 7. There is an open issue about how to fix problems like the above. 1. Andreas stated that not maintaining our own custom scripts is a good aim, and some of the issues above could be handled with a one time fix at conversion time 2. Daisy & Tom stated that they preferred such issues to be fixed in the toolchain 3. Just looking at the "** STRING **" issue, it's 70 strings but a quick proof of concept didn't result in fixing the issue - we haven't worked out why yet. 4. The current toolchain is difficult to modify, since it relies on an upstream component that is used by multiple projects, meaning post processing and pre-processing are the only real approach we have 5. It could be complicated to use post-processing and pre-processing to implement fixes for issues beyond the trivially updated string example in the current toolchain 8. There is an open question about whether it is possible to deliver an improved i18n experience with the current toolchain 9. There is not yet agreement that the current documentation toolchain is meeting the needs of the i18n team Based on the meeting, and especially the fact that due to inadequate communication the i18n team (inc Daisy) has not yet had the opportunity to assess the RST documentation toolchain fully, I would propose that the removal of existing guides and publication of RST guides be delayed until that's happened. We suggest that Daisy does an initial assessment and arrange a meeting to discuss next steps as soon as possible.There are many things we can fix with the the toolchain any time after publication, however it is important that we assess what needs to be done and ensure that we can actually feasibly deliver an improved experience for our translations, as well as our doc team. Regards, Tom

6 11

北京约克仪器公司上海
by 谈辛海 15 Apr '15

15 Apr '15

wxawryvz 16:56:58 2015/4/15

1 0

IRC meeting tomorrow
by Ying Chun Guo 15 Apr '15

15 Apr '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. Following topics will be covered: * rst document translation discussion with doc team * Final push on Horizon translation There is a wiki page [1] highlighting typical rst markups used by openstack manuals. Please go through it before the meeting. Thank you. Best regards Ying Chun Guo (Daisy) [1]https://wiki.openstack.org/wiki/I18nTeam/rst-markups

1 0

What's Up Doc? Apr 10 2015
by Anne Gentle 12 Apr '15

12 Apr '15

Hi all, As you probably saw from PTL nominations last week, I'm happy to hand the docs PTL baton to Lana Brindley! I loved leading this group and thank you all for supporting me. Thank you Lana for your willingness to lead. I'm still here to bring us to the Kilo release, so this week's What's Up Doc brings sharp focus requests to everyone to work on docs. These are the top priorities that we all need to work on - devs, writers, testers, gaters, everyone. 1. Bug triaging and fixing, especially for openstack-manuals. There are nearly 300 DocImpact bugs logged that we need developers to circle back to. With nearly 600 bugs overall, we need lots of focus here. To that end, I propose we hold a bug triage day. I'll send details in a separate email. 2. Install Guide testing and reviewing. The Install Guide team has a published spec that will help reviewers see what's changing with the Kilo Install guide: http://specs.openstack.org/openstack/docs-specs/specs/kilo/installguide-kil… Join them for weekly meetings Tuesdays at at 13:00 UTC (8:00 AM US CDT) in Google Hangout: https://plus.google.com/hangouts/_/calendar/a2FyaW4ua2F0aG9kZUBnbWFpbC5jb20… If you do nothing else but these two focus areas we'll be in good shape. There are other activities going on leading up to Vancouver but those two are top priorities. _RST Migration_ We are working to resolve translation tool expectations with the i18N team. I want to publish the RST-based English End User Guide and Admin User Guide once we're all comfortable with the way forward. Daisy will discuss the implications at the next i18N team meeting Thursday at 0800 UTC, and we'll implement and communicate the plan. _Networking Guide_ Next on the list is Networking Guide testing and reviewing. The Networking Guide team has a talk in Vancouver and needs to get their guide in shape for publishing. The neutron team is holding a doc day April 23. Please join in -- they'll post details in their notes. _First App Tutorial_ There's also the First Application Tutorial that needs to finish the spec and needs an editing cleanup prior to publishing. Ideally that will happen before Vancouver, we need to get it to the finish line. _HA Guide_ With everything else going on we need an updated spec for the HA Guide - the wiki page isn't enough. Based on this week's doc team meeting it sounds like that can go to RST as well but we need it in the spec so we can plan and cross-coordinate with the other priorities leading up to Vancouver. _Vancouver Summit _ The docs team has four Fishbowl time slots, 2 Workroom slots, and 1 Meetup allocated now. If you'd like to discuss a cross-project idea, please use the form to suggest new ideas: http://goo.gl/forms/S69HM6XEeb. You can see the current suggestions already posted here: https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5l… Lana or I will send out an etherpad in the next week or so with topic suggestions for our allocation. Thanks, Anne -- Anne Gentle annegentle(a)justwriteclick.com

3 3

User Guides Changes
by Andreas Jaeger 09 Apr '15

09 Apr '15

The two User Guide, Admin User Guide and End User Guide, have been converted from Docbook XML to RST. The conversion shouldn't have changed sentences but since markup has changed, strings for translation have changed as well. I've tried to merge the strings in transifex, so please have a look - and update the guides. I've marked the old guides as read-only in transifex, so that you cannot change them anymore but still can use them as reference. The documentation team will remove the old-guides from their project today. Transifex resources: Old End User Guide: https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/user-g… Old Admin User Guide: https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/user-g… New RST User Guides (single resource for both books): https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/user-g… If there's anything else I can do, please speak up, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

5 21

Horizon/Kilo, string freeze?
by Robert Simai 09 Apr '15

09 Apr '15

Hi, I was working on translations for Horizon/Kilo through Transifex during the last weeks and I've noticed there were at least 2 updates during the last few days, about 20 new strings have been added after I was on 100% done. I thought there should be some string freeze!? Anyone knows how this is supposed to work or better when to expect the final set of strings? -- Thanks, Robert

3 7

IRC meeting tomorrow
by Ying Chun Guo 02 Apr '15

02 Apr '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Status update of Horizon translation and issue collections * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

2 1

Does anyone want to update Juno Horizon translation for the next stable update?
by Akihiro Motoki 02 Apr '15

02 Apr '15

Juno 2014.2.3 stable release will be freezed Apr 2nd. Does anyone want to update your translations in Horizon? If no response, I won't take no action (without checking Transifex diff). If you want, please let me know by Friday (in UTC timezone). Thanks, Akihiro

4 3

[glance] bug 1436275/string freeze
by stuart.mclaren＠hp.com 27 Mar '15

27 Mar '15

Hi, I understand that the doc/source part of this patch: https://review.openstack.org/#/c/130222 doesn't impact the string freeze, but it also changes a couple of print statements so I'm sending notification as per the string freeze wiki page. Thanks, -Stuart

1 0

Checking PO Files before uploading in Transifex
by chandrakant dhutadmal 26 Mar '15

26 Mar '15

Hi. How does one check if the translated PO file is up to the expectation of the developer ? It is better to cross check the po file before uploading it on Transifex. What are the general "take care" points while translating OpenStack files ? Any pointers. Regards,Chandrakant Dhutadmal.

3 2

[Keystone] String Freeze Exceptions for Feature Freeze Exception BPs
by Morgan Fainberg 25 Mar '15

25 Mar '15

There are Feature Freeze Exception BPs [1][2][3] for Keystone that will cause string changes after string freeze. I am bringing these to the attention of this list per the wiki [4]. [1] https://blueprints.launchpad.net/keystone/+spec/domain-config-ext [2] https://blueprints.launchpad.net/keystone/+spec/idp-id-registration [3] https://blueprints.launchpad.net/keystone/+spec/ecp-wrapped-saml-assertions [4] https://wiki.openstack.org/wiki/StringFreeze

2 2

Re: [Openstack-i18n] [openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place
by ashish.jain14＠wipro.com 24 Mar '15

24 Mar '15

Hello, Moving this mails from openstack-dev to docs/i18n list. Please see the details below: I have submitted a patch to address the bug(https://bugs.launchpad.net/glance/+bug/1414725). This patch updates glance-manage documentation. Currently the documentation misses details on handling the glance-manage metadata definitions. I have submitted https://review.openstack.org/#/c/166597/ which addresses this deficiency in the documentation. Is it possible to include this change in the latest kilo documentation while the string freeze is in place? Regards Ashish -----Original Message----- From: Nikhil Komawar [mailto:nikhil.komawar@RACKSPACE.COM] Sent: Tuesday, March 24, 2015 12:53 AM To: openstack-dev(a)lists.openstack.org Subject: Re: [openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place Please direct this query to documentation and i18n lists [1, 2, 3] and include the response (if any) as a comment on the review so that the core reviewers are aware. Thanks for bringing this up and helping in contributing to the project! [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs [2] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n [3] https://wiki.openstack.org/wiki/Mailing_Lists Thanks, -Nikhil ________________________________________ From: ashish.jain14(a)wipro.com <ashish.jain14(a)wipro.com> Sent: Monday, March 23, 2015 1:01 PM To: openstack-dev(a)lists.openstack.org Subject: [openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place Hello, I have submitted a patch to address the bug(https://bugs.launchpad.net/glance/+bug/1414725). This patch updates glance-manage documentation. Currently the documentation misses details on handling the glance-manage metadata definitions. I have submitted https://review.openstack.org/#/c/166597/ which addresses this deficiency in the documentation. Is it possible to include this change in the latest kilo documentation while the string freeze is in place. Regards Ashish The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 1

Horizon translation check site for Kilo
by Akihiro Motoki 19 Mar '15

19 Mar '15

Hi, Kilo-3 is approaching and it is the time to start translations for Kilo. I would like to know the status of the community effort on preparing the Horizon translation check site. In the past releases, I18N team has the horizon translation check site but it was completely provided by my resource and time. For Kilo cycle, I am sure I can provide such site at all because I am spending very busy days on my main work. The same situation continues for three release cycles and I think it is time we should have such site as the team. We should not depend on someone's personal effort as OpenStack community. I may be able to provide the site for Kilo release if I have time but not sure. I would like to raise this topic. If nobody other than me raises a hand, it is no longer a team and it means we fail as a community. I can help the work but don't have enough time to lead it. I hope we have a progress on it. Thanks, Akihiro

6 11

Horizon translation for Kilo starts !
by Ying Chun Guo 19 Mar '15

19 Mar '15

Hello, all As OpenStack Kilo development draws to a close, it's time for our translators to start one of our major works: translating OpenStack Dashboard into multiple languages. Till now, around 558 new strings are added since Juno to Kilo. The official date of Kilo release is April 30. We'd better to finish the translations before April 20, in order to reserve enough times to merge the translations into the final release. I did a check of the translation website: https://www.transifex.com/projects/p/horizon/ The translations of following languages have been completed more than a half. Their translations are most likely completed by April 20. They are: Korean (Korea) 55 strings left Japanese 316 strings left German 487 strings left Chinese (China) 558 strings left French 558 strings left Portuguese (Brazil) 558 strings left Spanish 558 strings left Kannada 747 strings left Russian 767 strings left Chinese (Taiwan) 830 strings left Polish (Poland) 870 strings left Hindi 1068 strings left Czech 1355 strings left Dutch (Netherlands) 1420 strings left Serbian 1433 strings left The contributions to other languages are welcomed too. There is still 1 month left. The strings in total is around 3300. If several friends/colleagues work together, it's very possible to complete The resources of Kilo release in Transifex are: Kilo - Horizon Java Script Translations (133 strings in total) https://www.transifex.com/projects/p/horizon/resource/horizon-js-translatio… Kilo - Horizon Translations (104 strings in total) https://www.transifex.com/projects/p/horizon/resource/horizon-translations/ Kilo - OpenStack Dashboard Translations (3141 strings in total) https://www.transifex.com/projects/p/horizon/resource/openstack-dashboard-t… Please join this most valuable and high priority work. Let's work together to help OpenStack dashboard speak multiple langauges ! Thank you and best regards Ying Chun Guo (Daisy)

1 0

IRC meeting tomorrow
by Ying Chun Guo 18 Mar '15

18 Mar '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Kick off Horizon translation for Kilo * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

2 1

Translating RST source with Sphinx builds
by Anne Gentle 10 Mar '15

10 Mar '15

Hi all, We're preparing to migrate user guides to RST to improve ease of authoring for documentation. The spec [1] is now published, and we've got a research item for a toolchain that can "slice" RST similar to the DocBook slicing we do now. Reading the Sphinx documentation, it seems that you can run sphinx-build -b get-text to extract translatable strings to get a collection of .po files. This seems very similar to our current docbook slicing script. Does anyone have time this release to go through the RST files we're creating with the Sphinx workflow and analyze the results? I don't intend to publish the RST-based user guides until we have agreement on the translation toolchain, so we have until April 9, but ideally we'll have answers this month -- originally on the spec I wanted answers by last month, but without a lot of complex RST to test there wasn't a great way to research. Now that we are getting more RST files in openstack/openstack-manuals/doc/playground-user-guide [3] I would appreciate help here. Thanks, Anne 1. http://specs.openstack.org/openstack/docs-specs/specs/kilo/migrate-to-new-w… 2. http://sphinx-doc.org/latest/intl.html

3 9

docs.openstack.org - What to put on translated pages?
by Andreas Jaeger 09 Mar '15

09 Mar '15

Reviewing https://review.openstack.org/#/c/162045, I noticed that the patch adds all manuals to it - so both the translated Korean ones as well as English titles. In the past, the translated pages only contained links to translated manuals but not to English ones. But I noticed that the Japanese index page was changed recently as well and puts up all the document. How do we want to continue here? My suggest would be to only list translated manuals on a localized index page to not confuse the users. Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

4 4

OpenStack interface in Indian languages
by chandrakant dhutadmal 07 Mar '15

07 Mar '15

Hi All. It gives me great pleasure in informing you all that C-DAC, Pune (Centre for development of advanced computing) has decided to contribute in translating OpenStack interface in all 22 Scheduled Indian languages. @Chandan Kumar has been helpful in getting started. Need to discuss this with language team leaders/ maintainers in order to avoid duplicate efforts. Please comment. RegardsChandrakant DhutadmalC-DAC, Pune.

4 17

I18n meeting tomorrow
by Ying Chun Guo 04 Mar '15

04 Mar '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Translation test discussion * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] [OpenStack-docs] [ha-guide] RST or Docbook?
by Anne Gentle 02 Mar '15

02 Mar '15

On Thu, Feb 26, 2015 at 3:38 PM, Nick Chase <nchase(a)mirantis.com> wrote: > We decided we'd take this to the mailing list, for obvious reasons. > > I vote RST. We do have a good bit of existing material, but it could > easily be converted to RST, and I know how to set it up, now that I've done > the Networking Guide. :) > > That said, where are we on the translation status? > I emailed Daisy earlier this week but haven't seen a reply (hopefully haven't just missed it.) Anyone else on the i18n list know where we are with testing RST/Sphinx and the translation toolchain? Anne > > Thanks... > > ---- Nick > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > -- Anne Gentle annegentle(a)justwriteclick.com

5 7

Re: [Openstack-i18n] [OpenStack-docs] I question html tag status in API Reference Document
by Andreas Jaeger 25 Feb '15

25 Feb '15

On 02/25/2015 09:41 AM, SungJin Kang wrote: > Hi, > I translation document to Korean. API Reference [1] > > this 'maxServerMeta' [2] is tag '<code>'. > this 'maxPersonality' [3] is tag 'no'. > > two attribute is different?? > > two attribute is same... added '<code>' tag?? Hi, I strongly advise to not translate the API reference document, it includes lots of WADL that our toolchain does not handle and thus you will never be able to fully translate the manual. That's why the guide has a tag "do-not-translate-yet", Andreas > Thanks, > Sungjin. > > > [1] : > https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/api-re… > [2]: > https://github.com/openstack/api-site/blob/master/api-ref/src/docbkx/ch_com… > [3]: > https://github.com/openstack/api-site/blob/master/api-ref/src/docbkx/ch_com… > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1