<html><body>
<p><font size="2" face="sans-serif">Hello,</font><br>
<br>
<font size="2" face="sans-serif">There was a meeting with translators in IRC.</font><br>
<font size="2" face="sans-serif">Andreas Jaeger and Lana Brindley from doc team attended.</font><br>
<font size="2" face="sans-serif">François Bureau from French team, SungJin Kang from Korean team </font><br>
<font size="2" face="sans-serif">and myself from Chinese team attended the meeting.</font><br>
<br>
<font size="2" face="sans-serif">Firstly, Andreas confirmed that the tool chain was extendable.</font><br>
<font size="2" face="sans-serif">The preprocessing of po/pot before translation could be implemented in tools/generatepot-rst.sh.</font><br>
<font size="2" face="sans-serif">The postprocessing of po after translation could be done either as part of the building process,</font><br>
<font size="2" face="sans-serif">or as part of the infra scripts - propose_translation_update_manuals.sh .</font><br>
<br>
<font size="2" face="sans-serif">Then we talked about how to translate those strings with rst markups.</font><br>
<font size="2" face="sans-serif">rst markups are more difficult to identified than XML tags.</font><br>
<font size="2" face="sans-serif">That's why a translators RST cheat sheet is needed.</font><br>
<font size="2" face="sans-serif">Andreas and Lana explained some markups to translators.</font><br>
<font size="2" face="sans-serif">At last, all the attendees from translation teams were fine with the rst conversion.</font><br>
<br>
<font size="2" face="sans-serif">I will continue to maintain the translators cheat sheet.</font><br>
<font size="2" face="sans-serif">If doc writers introduce new mark ups, don't forget to add to the cheat sheet.</font><br>
<font size="2" face="sans-serif">The sheet can help the new translators easily understand how to translate.</font><br>
<br>
<font size="2" face="sans-serif">I think we got the agreement to go on.</font><br>
<font size="2" face="sans-serif">Many thanks to the attendees.</font><br>
<br>
<font size="2" face="sans-serif">Best regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<br>
<tt><font size="2">Ying Chun Guo/China/IBM@IBMCN wrote on 2015/04/10 17:04:38:<br>
<br>
> From: Ying Chun Guo/China/IBM@IBMCN</font></tt><br>
<tt><font size="2">> To: Andreas Jaeger <aj@suse.com></font></tt><br>
<tt><font size="2">> Cc: "openstack-i18n@lists.openstack.org" <openstack-<br>
> i18n@lists.openstack.org>, "openstack-docs@lists.openstack.org" <br>
> <openstack-docs@lists.openstack.org></font></tt><br>
<tt><font size="2">> Date: 2015/04/10 17:09</font></tt><br>
<tt><font size="2">> Subject: Re: [OpenStack-docs] [Openstack-i18n] Status of the RST <br>
> Documentation Toolchain</font></tt><br>
<tt><font size="2">> <br>
> Here are my thoughts.<br>
> <br>
> 1. I would like the toolchain could be extendable for the future improvement.<br>
> If we are able to make small and easy improvements before publishing, <br>
> like handling double stars and double colons (described in [1]), <br>
> let's do that.<br>
> In the future, let's continue the improvement. The goal is to provide an<br>
> easily understandable source strings for translators. <br>
> <br>
> 2. I would like the translators to be well educated about the RST markups.<br>
> I will covert [2] into translators' view.<br>
> ( I don't think translators would read through this long document to<br>
> pick out RST markups. )<br>
> Clearly list RST markups, give samples, and describe the meanings.<br>
> Thus the translators could easily understand which words and <br>
> punctuation characters<br>
> should not be translated and need to keep them unchanged carefully.<br>
> <br>
> 3. Next Thursday, I will have the team meeting with the translators. I will <br>
> collect their feedback to these RST markups. <br>
> <br>
> @ Andreas and Anne, let me know your feeling tho these thoughts.<br>
> <br>
> Daisy<br>
> <br>
> [1] <a href="http://lists.openstack.org/pipermail/openstack-i18n/2015-April/001030.html">http://lists.openstack.org/pipermail/openstack-i18n/2015-April/001030.html</a><br>
> [2] <a href="https://wiki.openstack.org/wiki/Documentation/Markup_conventions">https://wiki.openstack.org/wiki/Documentation/Markup_conventions</a><br>
> <br>
> Andreas Jaeger <aj@suse.com> wrote on 2015/04/10 12:38:21:<br>
> <br>
> > From: Andreas Jaeger <aj@suse.com><br>
> > To: Ying Chun Guo/China/IBM@IBMCN<br>
> > Cc: "openstack-i18n@lists.openstack.org" <openstack-<br>
> > i18n@lists.openstack.org>, "openstack-docs@lists.openstack.org" <br>
> > <openstack-docs@lists.openstack.org><br>
> > Date: 2015/04/10 12:38<br>
> > Subject: Re: [OpenStack-docs] [Openstack-i18n] Status of the RST <br>
> > Documentation Toolchain<br>
> > <br>
> > On 04/09/2015 02:16 PM, Ying Chun Guo wrote:<br>
> > > [...]<br>
> > > I investigated the translation process of RST document, asked by Anne<br>
> > > and Andreas.<br>
> > > While I made test, I used playground-user-guide, which was a quite new<br>
> > > document.<br>
> > > I didn't pay attention to the pot content changes between the old<br>
> > > version and the new version.<br>
> > > I'm quite sorry for that.<br>
> > > I don't want to block anything.<br>
> > > In my mind, the toolchain could be improved continuously,<br>
> > > both before publication and after publication.<br>
> > <br>
> > With the analysis done by Daisy [1] (thanks!) and my scripted updates to <br>
> > convert automatically what was possible [2] thus raising the number of <br>
> > translated strings for Japanese on the User Guides from 32 % to 37 %, <br>
> > and my patch for building the Japanese tools we have IMHO done <br>
> > everything we can do.<br>
> > <br>
> > Or has anybody suggestions for additional things to do now?<br>
> > <br>
> > If not, I think we're good to publish the new RST User Guides.<br>
> > <br>
> > So, I propose these next steps:<br>
> > * Get explicit ok by Daisy that we can continue based on her findings<br>
> > * Review and merge patch [3]<br>
> > * Anne decides when to publish User Guides<br>
> > <br>
> > Andreas<br>
> > <br>
> > [1] <br>
> > <a href="http://lists.openstack.org/pipermail/openstack-i18n/2015-April/001030.html">http://lists.openstack.org/pipermail/openstack-i18n/2015-April/001030.html</a><br>
> > [2] <br>
> > <a href="http://lists.openstack.org/pipermail/openstack-i18n/2015-April/001034.html">http://lists.openstack.org/pipermail/openstack-i18n/2015-April/001034.html</a><br>
> > [3] <a href="https://review.openstack.org/162424">https://review.openstack.org/162424</a><br>
> > -- <br>
> > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi<br>
> > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> > GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,<br>
> > Graham Norton, HRB 21284 (AG Nürnberg)<br>
> > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
> > _______________________________________________<br>
> OpenStack-docs mailing list<br>
> OpenStack-docs@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</font></tt></body></html>