<div dir="ltr"><div>Hi Andreas,<br><br></div>Thanks your for inputs, I am planning to keep the re-use part after Juno2. I think the amount of work required for getting this to a comfortable place is quite tedious. May be being the first project to attempt the same is also a factor. I will be working on this issue and solve it. I think that may be the issue here.<br>
<br>Regards,<br>Pranav<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jul 19, 2014 at 9:40 PM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="">On Sat, Jul 19, 2014 at 2:56 AM, Pranav Salunke <span dir="ltr"><<a href="mailto:dguitarbite@gmail.com" target="_blank">dguitarbite@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Andreas,<br><br>I am working on the xi:include part. I need it desperately to provide basic-install-guides under training manuals by linking the content from install guides. I believe that once this initial work is done, we could also offshore different sections to existing manuals books. Do I need to be aware of anything for translations to work?<br>
</div></blockquote><div><br></div></div><div>Hi Pranav,</div><div>Thanks for trying this out. To answer your question, let's make sure you know how the install guides work. They are sourced to create four guides with conditionals for each operating system such as <span style="color:rgb(0,0,0);font-size:14px"> </span><span style="font-size:14px;color:rgb(131,0,0)">os</span><span style="color:rgb(0,0,0);font-size:14px">=</span><span style="font-size:14px;color:rgb(255,0,0)">"ubuntu;debian"</span></div>
<div>as an attribute on any element you want to only be output with those two guides, Ubuntu and Debian.</div><div><br></div><div>Translators can still translate those elements, of course, and it saves us time and effort. </div>
<div><br></div><div>But then the training guides will still have to be output with conditional builds.</div><div><br></div><div>I was thinking about the problem you're seeing with the references to the "plain" URL on the <a href="http://git.openstack.org" target="_blank">git.openstack.org</a> site for png files, such as <a href="http://git.openstack.org/cgit/openstack/openstack-manuals/plain/doc/user-guide-admin/figures/cloud_dash_users_list.png" target="_blank">http://git.openstack.org/cgit/openstack/openstack-manuals/plain/doc/user-guide-admin/figures/cloud_dash_users_list.png</a> and I think the root cause of the problem is when the reference to the figure is conditional. </div>
<div><br></div><div>Conditional means that it's output only when the maven plugin calls for it, such as building just the SUSE install or just the Debian install guide. So when you're doing xi:include of only Ubuntu, but the build is still somehow picking up the debian conditionals for example, then the build might fail. </div>
<div><br></div><div>So that's what I'd say to be aware of that's special for the install guide for now. </div><div><br></div><div>There's also Shaun's work on the toolchain to support ITS markup so that translators know which elements not to translate (like userinput, screen, prompt, etc.) but we are not doing that markup currently.</div>
<div><br></div><div>Thanks,</div><div>Anne</div><div class=""><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<br>Regards,<br>Pranav<br></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Wed, Jul 16, 2014 at 3:04 PM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div>On 07/08/2014 04:18 PM, Andreas Jaeger wrote:<br>
> My patches are a start to get the ball rolling. The files you xi:include<br>
> from openstack-manuals will need some creative development, somebody<br>
> needs to look into that at one point,<br>
<br>
</div>Patches are in, translators can start if they like,<br>
<br>
Andreas<br>
<span><font color="#888888">--<br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
</font></span></div></div><div><div><div><div> 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></div></div><div>
_______________________________________________<br>
Openstack-i18n mailing list<br>
<a href="mailto:Openstack-i18n@lists.openstack.org" target="_blank">Openstack-i18n@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
</div></div></div></blockquote></div><br></div>
</blockquote></div></div><br></div></div>
</blockquote></div><br></div>