<html><body>
<p><tt><font size="2">Andreas Jaeger <aj@suse.com> wrote on 2014/08/22 15:16:30:<br>
<br>
> Andreas Jaeger <aj@suse.com> </font></tt><br>
<tt><font size="2">> 2014/08/22 15:16</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Ying Chun Guo/China/IBM@IBMCN, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org></font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-i18n] Glossary clarification?</font></tt><br>
<tt><font size="2">> <br>
> On 08/22/2014 07:39 AM, Ying Chun Guo wrote:<br>
> > Hi, Andreas<br>
> > <br>
> > Thank you for asking.<br>
> > My question is:<br>
> > I see glossary is a part of documents, not a single document.<br>
> <br>
> It's published on its own as reference in a "hidden" way:<br>
> <a href="http://docs.openstack.org/glossary/">http://docs.openstack.org/glossary/</a><br>
> <br>
> > If we translate glossary, could it be published alone? How could<br>
> > translators see their results of work?<br>
> <br>
> We can always use the drafts-i18n page to publish it.<br>
> <br>
> > I had a talk with Tom Fifiled.<br>
> > He helped to address these questions:<br>
> <br>
> Great.<br>
> <br>
> > There is one XML file that includes all glossary terms.<br>
> > When a book uses a glossary term inside, doc authors mark it with some<br>
> > special syntax, eg. <glossterm>account</glossterm>,<br>
> > This generates a custom glossary for each book.<br>
> > This is why I see a different glossary for each book.<br>
> <br>
> Also, the glossary entries are shown directly if you hover over them,<br>
> see<br>
> <a href="http://docs.openstack.org/trunk/install-guide/install/zypper/">http://docs.openstack.org/trunk/install-guide/install/zypper/</a><br>
> content/ch_overview.html<br>
> and look at the amber boxes.<br>
> <br>
> > That entire file is actually published to<br>
> > <a href="http://docs.openstack.org/glossary/">http://docs.openstack.org/glossary/</a>.<br>
> > If glossary-terms.xml is translated<br>
> > (<a href="https://github.com/openstack/openstack-manuals/tree/master/doc/glossary">https://github.com/openstack/openstack-manuals/tree/master/doc/glossary</a>),<br>
> > then all books will have a translated glossary and that particular<br>
> > special page will also be translated.<br>
> > Note also: the operations guide has a copy of the glossary. This is<br>
> > automatically copied. It is an identical file.<br>
> > (<a href="https://github.com/openstack/operations-guide/tree/master/doc/glossary">https://github.com/openstack/operations-guide/tree/master/doc/glossary</a>)<br>
> > So only glossary-terms.xml in the openstack-manuals/doc/glossary folder<br>
> > needs translation.<br>
> > Translations will also be automatically copied to operations-guide<br>
> > repository.<br>
> > <br>
> > I also talked with Tom about how to display the localized glossary.<br>
> > If the localized glossary could be displayed with both English terms and<br>
> > localized terms, it will be wonderful.<br>
> > i.e. English term is ahead, localized term is followed in a same line,<br>
> > Below is the explanation, completed localized.<br>
> > <br>
> > The localized glossary page will include the mapping information between<br>
> > English term to localized term.<br>
> > And the terms could be sorted in English alphabetical order.<br>
> > That will be display a great localized glossary.<br>
> > But we need write some scripts to implement such function.<br>
> <br>
> Yeah, this might need some extra scripting.<br>
> <br>
> > Any thoughts or comments?<br>
> <br>
> I'm not sure how to do this glossary translation best - but you should<br>
> be aware of it since it will give you only partial translated manuals...<br>
> </font></tt><br>
<br>
<tt><font size="2">What do you mean by "partial translated manuals" ?</font></tt><br>
<tt><font size="2"><br>
> Andreas<br>
> -- <br>
> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi<br>
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
> <br>
</font></tt></body></html>