<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="ace-line" id="magicdomid51"><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Hi,</span></div>
<div class="ace-line" id="magicdomid53"><br>
</div>
<div class="ace-line" id="magicdomid6793"><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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!</span></div>
<div class="ace-line" id="magicdomid405"><br>
</div>
<div class="ace-line list-start-number1" id="magicdomid9002">
<ol start="1" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Everyone
involved wants to make translators happy, and hopes that the
process of moving to RST can deliver an improved toolchain</span></li>
</ol>
</div>
<div class="ace-line" id="magicdomid9003">
<ol start="2" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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</span></li>
</ol>
</div>
<div class="ace-line" id="magicdomid9004">
<ol start="3" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Previous
statement that RST-based docs would not be published without
agreement on the translation toolchain was acknowledged</span></li>
</ol>
</div>
<div class="ace-line" id="magicdomid9005">
<ol start="4" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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</span></li>
</ol>
</div>
<div class="ace-line" id="magicdomid9006">
<ol start="5" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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 </span><span
class="author-a-0z81zz65zfz71zz122z3z70za0fpz75znm1">initial
version of </span><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">guides
in the playground </span><span
class="author-a-0z81zz65zfz71zz122z3z70za0fpz75znm1">folder</span></li>
</ol>
</div>
<div class="ace-line" id="magicdomid9007">
<ol start="6" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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:</span></li>
</ol>
</div>
<blockquote>
<div class="ace-line list-start-number2" id="magicdomid9008">
<ol start="1" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Strings
that should have been trivially updated during conversion
from docbook without human interaction needed (eg
**string**\n)</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9009">
<ol start="2" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Strings
that are entirely markup (eg
:ref:`Boot_instance_from_image_and_attach_non-bootable_volume`)</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9010">
<ol start="3" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Strings
that contain significant amounts of markup</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9011">
<ol start="4" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Strings
that contain markup characters that are unusual for
translations, eg backticks, asterisks</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9012">
<ol start="5" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Strings
that contain markup where placeholders were previously
used</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9013">
<ol start="6" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">...
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</span></li>
</ol>
</div>
</blockquote>
<div class="ace-line" id="magicdomid9014">
<ol start="7" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">There
is an open issue about how to fix problems like the above.</span></li>
</ol>
</div>
<blockquote>
<div class="ace-line list-start-number2" id="magicdomid9015">
<ol start="1" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9016">
<ol start="2" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Daisy
& Tom stated that they preferred such issues to be
fixed in the toolchain</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9039">
<ol start="3" class="list-number2">
<li><span class="author-a-0z81zz65zfz71zz122z3z70za0fpz75znm1">Just
looking at the "** STRING **" issue, it's 70 strings but a
quick proof of concept d</span><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">idn't
result in fixing the issue - we haven't worked out why
yet.</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9018">
<ol start="4" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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</span></li>
</ol>
</div>
</blockquote>
<blockquote>
<div class="ace-line" id="magicdomid9019">
<ol start="5" class="list-number2">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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</span></li>
</ol>
</div>
</blockquote>
<div class="ace-line" id="magicdomid9020">
<ol start="8" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">There
is an open question about whether it is possible to deliver
an improved i18n experience with the current toolchain</span></li>
</ol>
</div>
<div class="ace-line" id="magicdomid9021">
<ol start="9" class="list-number1">
<li><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">There
is not yet agreement that the current documentation
toolchain is meeting the needs of the i18n team</span></li>
</ol>
</div>
<div class="ace-line" id="magicdomid6404"><br>
</div>
<div class="ace-line" id="magicdomid6421"><br>
</div>
<div class="ace-line" id="magicdomid9040"><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">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.</span></div>
<div class="ace-line" id="magicdomid10050"><span
class="author-a-0z81zz65zfz71zz122z3z70za0fpz75znm1">We suggest
that Daisy does an initial assessment </span><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">and
arrange a meeting to discuss next steps as soon as possible</span><span
class="author-a-0z81zz65zfz71zz122z3z70za0fpz75znm1">.</span><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax"> 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.</span></div>
<div class="ace-line" id="magicdomid10040"><br>
</div>
<div class="ace-line" id="magicdomid10039"><br>
</div>
<div class="ace-line" id="magicdomid416"><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Regards,</span></div>
<div class="ace-line" id="magicdomid418"><br>
</div>
<div class="ace-line" id="magicdomid419"><br>
</div>
<div class="ace-line" id="magicdomid421"><span
class="author-a-a4z90z0z82zu1z76z4z68zz82zz82zz89zz74zax">Tom</span></div>
<div class="ace-line" id="magicdomid12"><br>
</div>
</body>
</html>