<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 2, 2014 at 4:29 AM, Tom Fifield <span dir="ltr"><<a href="mailto:tom@openstack.org" target="_blank">tom@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 class="im">On 31/12/13 12:00, Anne Gentle wrote:<br>
> All sounds right to me, including Andreas's head start on step 0.<br>
><br>
><br>
><br>
><br>
> On Mon, Dec 30, 2013 at 8:34 AM, Andreas Jaeger <<a href="mailto:aj@suse.com">aj@suse.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:aj@suse.com">aj@suse.com</a>>> wrote:<br>
><br>
> On 12/30/2013 02:37 PM, Tom Fifield wrote:<br>
> > Hi all,<br>
> ><br>
> > I've been contacted by someone who might have resources to do some<br>
> > translation of the api reference. However, I'm not 100% clear on the<br>
> > tooling changes required.<br>
> ><br>
> > It looks like we need to<br>
> ><br>
> > 0) change infra, so that openstack-doc-tools is available to jobs<br>
> in the<br>
> > openstack-api-site repo<br>
><br>
> Yeah, I'm working on that part and currently are blocked by an infra<br>
> review ( <a href="https://review.openstack.org/#/c/62984/" target="_blank">https://review.openstack.org/#/c/62984/</a> ).<br>
><br>
> I've also done over the last days quite some changes to<br>
> openstack-doc-tools so that it can gate the api-site repo.<br>
><br>
> Reviews are welcome:<br>
> <a href="https://review.openstack.org/#/q/status:open+project:openstack/openstack-doc-tools,n,z" target="_blank">https://review.openstack.org/#/q/status:open+project:openstack/openstack-doc-tools,n,z</a><br>
><br>
> Thanks,<br>
> Andreas<br>
><br>
> > 1) make openstack-doc-tools/bin/generatepot work with the WADL format,<br>
> > if it doesn't already<br>
><br>
><br>
> One thought here is that the text that would be translated may already<br>
> be in the docbook markup, so hopefully there won't be much work to do here.<br>
<br>
</div>*fingers crossed*<br>
<div class="im"><br>
><br>
> > 2) change infra, so that changes to openstack-api-site are<br>
> propogated to<br>
> > the translation system, like they are already for openstack-manuals<br>
> ><br>
> > did I miss anything?<br>
><br>
><br>
> One additional thought is that the html output for api-ref.html hasn't<br>
> had any translation consideration at all for wrapping, text size, fonts,<br>
> and so on. Also, it's possible that the table titles are encoded in the<br>
> xslts themselves. Diane and David may know more.<br></div></blockquote><div><br></div><div>I talked to David and he said there are English words and phrases that would need to be parameterized and call an external translated file. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
</div>A good point! I wonder how it will look :D<br>
<div class="im"><br>
> Also, one last thought, I'd like to know more about the reason for<br>
> prioritizing an API reference so highly? I thought that other<br>
> translation efforts hadn't prioritized API info as high as other items,<br>
> so I'm curious about the audience and their need. If they're SDK devs<br>
> that's great. Or if user guides and other guides are already done and<br>
> they're looking for more to translate, that's cool too. Just want to<br>
> know more background if you can share.<br>
<br>
</div>This is the desire of the organisation with resources :) I guess it<br>
comes from customer requirements. Though, of course we're also going to<br>
try and rope anyone and everyone in to other documents more in line with<br>
the project priorities wherever we can - if someone wants to translate<br>
something specific, we should support IMO! :)<br>
<div class="im"><br></div></blockquote><div><br></div><div>Certainly, not saying anything but that, just wanting to know more. Contact me privately if that's the desire of the translators.</div><div><br></div><div>Thanks,</div>
<div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
><br>
> Anne<br>
><br>
><br>
> ><br>
> ><br>
> ><br>
> > Regards,<br>
> ><br>
> ><br>
> > Tom<br>
> ><br>
> > _______________________________________________<br>
> > Openstack-docs mailing list<br>
> > <a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
</div>> <mailto:<a href="mailto: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>
> ><br>
><br>
><br>
> --<br>
> Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a> <<a href="http://suse.com" target="_blank">http://suse.com</a>>,<a href="http://opensuse.org" target="_blank">opensuse.org</a><br>
> <<a href="http://opensuse.org" target="_blank">http://opensuse.org</a>>} Twitter/Identica: jaegerandi<br>
<div class="im">> 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>
> _______________________________________________<br>
> Openstack-docs mailing list<br>
> <a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
</div>> <mailto:<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a>><br>
<div class="im">> <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>
><br>
><br>
><br>
><br>
> --<br>
> Anne Gentle<br>
</div>> <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a> <mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>><br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div></div>