<html><body>
<p><font size="2" face="sans-serif">Here are my thoughts.</font><br>
<br>
<font size="2" face="sans-serif">1. I would like the toolchain could be extendable for the future improvement.</font><br>
<font size="2" face="sans-serif">If we are able to make small and easy improvements before publishing, </font><br>
<font size="2" face="sans-serif">like handling double stars and double colons (described in [1]), let's do that.</font><br>
<font size="2" face="sans-serif">In the future, let's continue the improvement. The goal is to provide an</font><br>
<font size="2" face="sans-serif">easily understandable source strings for translators.</font><font size="3" face="serif"> </font><br>
<br>
<font size="2" face="sans-serif">2. I would like the translators to be well educated about the RST markups.</font><br>
<font size="2" face="sans-serif">I will covert [2] into translators' view.</font><br>
<font size="2" face="sans-serif">( I don't think translators would read through this long document to pick out RST markups. )</font><br>
<font size="2" face="sans-serif">Clearly list RST markups, give samples, and describe the meanings.</font><br>
<font size="2" face="sans-serif">Thus the translators could easily understand which words and punctuation characters</font><br>
<font size="2" face="sans-serif">should not be translated and need to keep them unchanged carefully.</font><br>
<br>
<font size="2" face="sans-serif">3. Next Thursday, I will have the team meeting with the translators. I will </font><br>
<font size="2" face="sans-serif">collect their feedback to these RST markups. </font><br>
<br>
<font size="2" face="sans-serif">@ Andreas and Anne, let me know your feeling tho these thoughts.</font><br>
<br>
<font size="2" face="sans-serif">Daisy</font><br>
<br>
<font size="2" face="sans-serif">[1] </font><tt><font size="2"><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></font></tt><br>
<font size="2" face="sans-serif">[2] </font><a href="https://wiki.openstack.org/wiki/Documentation/Markup_conventions"><font size="2" face="sans-serif">https://wiki.openstack.org/wiki/Documentation/Markup_conventions</font></a><br>
<font size="2" face="sans-serif"> </font><br>
<tt><font size="2">Andreas Jaeger <aj@suse.com> wrote on 2015/04/10 12:38:21:<br>
<br>
> From: Andreas Jaeger <aj@suse.com></font></tt><br>
<tt><font size="2">> To: Ying Chun Guo/China/IBM@IBMCN</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 12:38</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>
> 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>
</font></tt></body></html>