April 2015 - OpenStack-I18n - lists.openstack.org

Update on Dogri, Konkani, Manipuri, Sanskrit, Santali
by Tom Fifield 14 May '15

14 May '15

Hi all, I just wanted to let you know that Transifex has added Dogri, Konkani, Manipuri, Sanskrit and Santali to their site's code repository, and will update the code of the live site (so we can use them) before the end of this month. Regards, Tom

2 4

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 22 Apr '15

22 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