<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Tom, I already did a pass at removing things that aren't common that are in the common directory. (We probably need another pass at that though.)</div>
<div><br>
</div>
<div>But why can't translators manage common files? I mean, on a book-by-book basis? If they translate the Install Guide, don't they translate the common files in that book? </div>
<div><br>
</div>
<div>Does it matter if everything in that folder is not translated?</div>
<div><br>
</div>
<div>
<div>
<div style="color: rgb(0, 0, 0); "><font class="Apple-style-span" color="rgb(0, 0, 0)" face="Apple Chancery"><i>Diane</i></font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); ">
<font class="Apple-style-span" color="rgb(0, 0, 0)"><i>----------------------------------------------</i></font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); ">
<font class="Apple-style-span" color="rgb(0, 0, 0)">Diane Fleming</font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="color: rgb(0, 0, 0); ">Software Developer II - US</div>
</div>
diane.fleming@rackspace.com</div>
<div>Cell 512.323.6799</div>
<div>Office 512.874.1260<br>
<span class="Apple-style-span" style="font-family: Calibri, sans-serif; ">
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="color: rgb(0, 0, 0); ">Skype drfleming0227</div>
<div style="color: rgb(0, 0, 0); ">Google-plus diane.fleming@gmail.com</div>
</div>
</span></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Nermina Miller <<a href="mailto:nerminamiller@gmail.com">nerminamiller@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, October 29, 2013 7:18 AM<br>
<span style="font-weight:bold">To: </span>Tom Fifield <<a href="mailto:tom@openstack.org">tom@openstack.org</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>" <<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-docs] proposed rst-xml automation openstack-manuals blueprint<br>
</div>
<div><br>
</div>
<div>
<div>Tom, these files could be kept in the currently proposed Sources folder within the Training Guides folder. Would that alleviate your concerns? However, these devref files contain valuable install information that could be included in other guides. I could
analyze them further to see how they could be appropriated. If there's no significant value that would make them xi:includable for other guides, then they could be hosted in the Training folder. The ultimate intent is to make them accessible and part of the
OS Docs family. I would think that translators would focus only on the files that are particular to a specific guide and not the entire Common folder. <span></span>I'll respond to Anne's comments shortly. - Nermina <br>
<br>
On Monday, October 28, 2013, Tom Fifield wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 29/10/13 11:45, Nermina Miller wrote:<br>
> - Add the entire batch of the devref files to the Common folder<br>
> (subfolder Training) so the files can be made available to the other<br>
> guides in the long term. (Why all? Because the py script updates and<br>
> converts them ALL at the same time. You may already know this but it<br>
> helps to explain the need for such a large batch.)<br>
<br>
This is a problem for translation.<br>
<br>
The common directory is already over 50,000 words - putting it beyond<br>
the reach of all but our most dedicated language teams. I've actually<br>
had a plan to try and move some material that really isn't 'common' out<br>
of there for this reason.<br>
<br>
Using common as a dumping ground will essentially prevent translation of<br>
the best parts of our manuals - those that have been lovingly crafted<br>
for use in several documents. Translators should be able to make maximum<br>
impact by translating items in common, but that's not true today.<br>
<br>
For a real example, take the install guide - it's just 18k words, a nice<br>
small guide and easy to translate. There's actually some good progress<br>
being made in several languages (more than 20% in Russian and Chinese).<br>
However, it also has some content from common, and working with the 50k<br>
mess to get a complete document out is pretty annoying.<br>
<br>
In short: please don't put stuff in common unless it is truly used by<br>
multiple documents, and especially don't use it as a dumping ground for<br>
large amounts of content.<br>
<br>
<br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'Openstack-docs@lists.openstack.org')">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</blockquote>
<br>
<br>
-- <br>
<div dir="ltr">Thank you!
<div><br>
</div>
<div>Nermina Miller</div>
<div>Tech Writer and Editor</div>
</div>
<br>
</div>
</div>
</span>
</body>
</html>