<div dir="ltr">Hello Ian, due the nature of the pot file format and mechanic<div>we cant add the translators as msgid entries bc will only exist on the corresponding po file per lang</div><div>said that , i think that we could create a solution using both [1] and [2]</div><div>that said</div><div>* adding "TRANSLATORS" msgid on pot file, so i could get that string per lang</div><div>* adding translators names as stated on [2] as po file metadata so i could parse and display per language</div><div><br></div><div><br></div><div>regards</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 1, 2018 at 11:03 PM, Ian Y. Choi <span dir="ltr"><<a href="mailto:ianyrchoi@gmail.com" target="_blank">ianyrchoi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Sebastian,<br>
<br>
Korean has also currently 100% translation now.<br>
About two weeks ago, there were a discussion how to include the list of translators per translated document.<br>
<br>
My proposal is mentioned in [1] - do you think it is a good idea and it is under implementation,<br>
or parsing the name of translators in header lines on po files (e.g., four lines on [2]) would be better idea?<br>
<br>
<br>
With many thanks,<br>
<br>
/Ian<br>
<br>
[1] <a href="http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.2018-07-19.log.html#t2018-07-19T15:09:46" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org<wbr>/irclogs/%23openstack-i18n/%<wbr>23openstack-i18n.2018-07-19.lo<wbr>g.html#t2018-07-19T15:09:46</a><br>
[2] <a href="http://git.openstack.org/cgit/openstack/i18n/tree/doc/source/locale/de/LC_MESSAGES/doc.po#n1" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/<wbr>openstack/i18n/tree/doc/source<wbr>/locale/de/LC_MESSAGES/doc.po#<wbr>n1</a><div><div class="h5"><br>
<br>
Frank Kloeker wrote on 7/31/2018 6:39 PM:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hi Sebastian,<br>
<br>
okay, it's translated now. In Edge whitepaper is the problem with XML-Parsing of the term AT&T. Don't know how to escape this. Maybe you will see the warning during import too.<br>
<br>
kind regards<br>
<br>
Frank<br>
<br>
Am 2018-07-30 20:09, schrieb Sebastian Marcet:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Frank,<br>
i was double checking pot file and realized that original pot missed<br>
some parts of the original paper (subsections of the paper) apologizes<br>
on that<br>
i just re uploaded an updated pot file with missing subsections<br>
<br>
regards<br>
<br>
On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker <<a href="mailto:eumel@arcor.de" target="_blank">eumel@arcor.de</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Jimmy,<br>
<br>
from the GUI I'll get this link:<br>
<br>
</blockquote>
<a href="https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/rest/file/translation/edge-<wbr>computing/pot-translation/de/<wbr>po?docId=cloud-edge-computing-<wbr>beyond-the-data-center</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[1]<br>
<br>
paper version are only in container whitepaper:<br>
<br>
<br>
</blockquote>
<a href="https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/rest/file/translation/levera<wbr>ging-containers-openstack/<wbr>paper/de/po?docId=leveraging-<wbr>containers-and-openstack</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[2]<br>
<br>
In general there is no group named papers<br>
<br>
kind regards<br>
<br>
Frank<br>
<br>
Am 2018-07-30 17:06, schrieb Jimmy McArthur:<br>
Frank,<br>
<br>
We're getting a 404 when looking for the pot file on the Zanata API:<br>
<br>
</blockquote>
<a href="https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/rest/file/translation/papers<wbr>/papers/de/po?docId=edge-<wbr>computing</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[3]<br>
<br>
As a result, we can't pull the po files. Any idea what might be<br>
happening?<br>
<br>
Seeing the same thing with both papers...<br>
<br>
Thank you,<br>
Jimmy<br>
<br>
Frank Kloeker wrote:<br>
Hi Jimmy,<br>
<br>
Korean and German version are now done on the new format. Can you<br>
check publishing?<br>
<br>
thx<br>
<br>
Frank<br>
<br>
Am 2018-07-19 16:47, schrieb Jimmy McArthur:<br>
Hi all -<br>
<br>
Follow up on the Edge paper specifically:<br>
<br>
</blockquote>
<a href="https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/iteration/view/edge-computin<wbr>g/pot-translation/documents?<wbr>dswid=-3192</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[4] This is now available. As I mentioned on IRC this morning, it<br>
should<br>
be VERY close to the PDF. Probably just needs a quick review.<br>
<br>
Let me know if I can assist with anything.<br>
<br>
Thank you to i18n team for all of your help!!!<br>
<br>
Cheers,<br>
Jimmy<br>
<br>
Jimmy McArthur wrote:<br>
Ian raises some great points :) I'll try to address below...<br>
<br>
Ian Y. Choi wrote:<br>
Hello,<br>
<br>
When I saw overall translation source strings on container<br>
whitepaper, I would infer that new edge computing whitepaper<br>
source strings would include HTML markup tags.<br>
One of the things I discussed with Ian and Frank in Vancouver is<br>
the expense of recreating PDFs with new translations. It's<br>
prohibitively expensive for the Foundation as it requires design<br>
resources which we just don't have. As a result, we created the<br>
Containers whitepaper in HTML, so that it could be easily updated<br>
w/o working with outside design contractors. I indicated that we<br>
would also be moving the Edge paper to HTML so that we could prevent<br>
that additional design resource cost.<br>
On the other hand, the source strings of edge computing whitepaper<br>
which I18n team previously translated do not include HTML markup<br>
tags, since the source strings are based on just text format.<br>
The version that Akihiro put together was based on the Edge PDF,<br>
which we unfortunately didn't have the resources to implement in the<br>
same format.<br>
<br>
I really appreciate Akihiro's work on RST-based support on<br>
publishing translated edge computing whitepapers, since<br>
translators do not have to re-translate all the strings.<br>
I would like to second this. It took a lot of initiative to work on<br>
the RST-based translation. At the moment, it's just not usable for<br>
the reasons mentioned above.<br>
On the other hand, it seems that I18n team needs to investigate on<br>
translating similar strings of HTML-based edge computing whitepaper<br>
source strings, which would discourage translators.<br>
Can you expand on this? I'm not entirely clear on why the HTML<br>
based translation is more difficult.<br>
<br>
That's my point of view on translating edge computing whitepaper.<br>
<br>
For translating container whitepaper, I want to further ask the<br>
followings since *I18n-based tools*<br>
would mean for translators that translators can test and publish<br>
translated whitepapers locally:<br>
<br>
- How to build translated container whitepaper using original<br>
Silverstripe-based repository?<br>
<a href="https://docs.openstack.org/i18n/latest/tools.html" rel="noreferrer" target="_blank">https://docs.openstack.org/i18<wbr>n/latest/tools.html</a> [5] describes<br>
well how to build translated artifacts for RST-based OpenStack<br>
repositories<br>
but I could not find the way how to build translated container<br>
whitepaper with translated resources on Zanata.<br>
This is a little tricky. It's possible to set up a local version<br>
of the OpenStack website<br>
<br>
</blockquote>
(<a href="https://github.com/OpenStackweb/openstack-org/blob/master/installation.md" rel="noreferrer" target="_blank">https://github.com/OpenStackw<wbr>eb/openstack-org/blob/master/<wbr>installation.md</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[6]). However, we have to manually ingest the po files as they are<br>
completed and then push them out to production, so that wouldn't do<br>
much to help with your local build. I'm open to suggestions on how<br>
we can make this process easier for the i18n team.<br>
<br>
Thank you,<br>
Jimmy<br>
<br>
With many thanks,<br>
<br>
/Ian<br>
<br>
Jimmy McArthur wrote on 7/17/2018 11:01 PM:<br>
Frank,<br>
<br>
I'm sorry to hear about the displeasure around the Edge paper. As<br>
mentioned in a prior thread, the RST format that Akihiro worked did<br>
not work with the Zanata process that we have been using with our<br>
CMS. Additionally, the existing EDGE page is a PDF, so we had to<br>
build a new template to work with the new HTML whitepaper layout we<br>
created for the Containers paper. I outlined this in the thread "<br>
[OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing<br>
Whitepaper Translation" on 6/25/18 and mentioned we would be ready<br>
with the template around 7/13.<br>
<br>
We completed the work on the new whitepaper template and then put<br>
out the pot files on Zanata so we can get the po language files<br>
back. If this process is too cumbersome for the translation team,<br>
I'm open to discussion, but right now our entire translation process<br>
is based on the official OpenStack Docs translation process outlined<br>
by the i18n team:<br>
<a href="https://docs.openstack.org/i18n/latest/en_GB/tools.html" rel="noreferrer" target="_blank">https://docs.openstack.org/i18<wbr>n/latest/en_GB/tools.html</a> [7]<br>
<br>
Again, I realize Akihiro put in some work on his own proposing the<br>
new translation type. If the i18n team is moving to this format<br>
instead, we can work on redoing our process.<br>
<br>
Please let me know if I can clarify further.<br>
<br>
Thanks,<br>
Jimmy<br>
<br>
Frank Kloeker wrote:<br>
Hi Jimmy,<br>
<br>
permission was added for you and Sebastian. The Container Whitepaper<br>
is on the Zanata frontpage now. But we removed Edge Computing<br>
whitepaper last week because there is a kind of displeasure in the<br>
team since the results of translation are still not published beside<br>
Chinese version. It would be nice if we have a commitment from the<br>
Foundation that results are published in a specific timeframe. This<br>
includes your requirements until the translation should be<br>
available.<br>
<br>
thx Frank<br>
<br>
Am 2018-07-16 17:26, schrieb Jimmy McArthur:<br>
Sorry, I should have also added... we additionally need permissions<br>
so<br>
that we can add the a new version of the pot file to this project:<br>
<br>
</blockquote>
<a href="https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/project/view/edge-computing/<wbr>versions?dswid=-7835</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[8] Thanks!<br>
Jimmy<br>
<br>
Jimmy McArthur wrote:<br>
Hi all -<br>
<br>
We have both of the current whitepapers up and available for<br>
translation. Can we promote these on the Zanata homepage?<br>
<br>
<br>
</blockquote>
<a href="https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/project/view/leveraging-cont<wbr>ainers-openstack?dswid=5684</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[9]<br>
<br>
</blockquote>
<a href="https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/iteration/view/edge-computin<wbr>g/master/documents?dswid=5684</a> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[10] Thanks all!<br>
Jimmy<br>
<br>
<br>
</blockquote>
______________________________<wbr>______________________________<wbr>______________ <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a> [11]<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
[12]<br>
</blockquote>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a> [11]<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a> [12]<br>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a> [11]<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a> [12]<br>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a> [11]<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a> [12]<br>
<br>
<br>
<br>
Links:<br>
------<br>
[1]<br>
<a href="https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/rest/file/translation/edge-<wbr>computing/pot-translation/de/<wbr>po?docId=cloud-edge-computing-<wbr>beyond-the-data-center</a> <br>
[2]<br>
<a href="https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/rest/file/translation/levera<wbr>ging-containers-openstack/<wbr>paper/de/po?docId=leveraging-<wbr>containers-and-openstack</a> <br>
[3]<br>
<a href="https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/rest/file/translation/papers<wbr>/papers/de/po?docId=edge-<wbr>computing</a> <br>
[4]<br>
<a href="https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/iteration/view/edge-computin<wbr>g/pot-translation/documents?<wbr>dswid=-3192</a> <br>
[5] <a href="https://docs.openstack.org/i18n/latest/tools.html" rel="noreferrer" target="_blank">https://docs.openstack.org/i18<wbr>n/latest/tools.html</a><br>
[6] <a href="https://github.com/OpenStackweb/openstack-org/blob/master/installation.md" rel="noreferrer" target="_blank">https://github.com/OpenStackwe<wbr>b/openstack-org/blob/master/<wbr>installation.md</a><br>
[7] <a href="https://docs.openstack.org/i18n/latest/en_GB/tools.html" rel="noreferrer" target="_blank">https://docs.openstack.org/i18<wbr>n/latest/en_GB/tools.html</a><br>
[8]<br>
<a href="https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/project/view/edge-computing/<wbr>versions?dswid=-7835</a> <br>
[9]<br>
<a href="https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/project/view/leveraging-cont<wbr>ainers-openstack?dswid=5684</a> <br>
[10]<br>
<a href="https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684" rel="noreferrer" target="_blank">https://translate.openstack.or<wbr>g/iteration/view/edge-computin<wbr>g/master/documents?dswid=5684</a> <br>
[11] <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@l<wbr>ists.openstack.org?subject:uns<wbr>ubscribe</a><br>
[12] <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
</div></div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
<br>
</blockquote></div><br></div>