Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-07 Thread Ian Y. Choi

Oh my mistake - document not version. Rewriting:

For the perspective on Stackalytics <-> the list of projects, another 
possible solution would be to create "openstack-org" project in Zanata,
migrate edge-computing & container whitepaper from two different 
projects into "openstack-org" project with different document names, and

adding "openstack-org" project in Stackalytics for consistency.


With many thanks,

/Ian



Ian Y. Choi wrote on 8/8/2018 12:06 AM:

Hello Frank,

I did not notice the list of project but just from the perspective of 
translation metrics in Stackalytics and Zanata,
whitepaper translation contribution is retrieved from Zanata to 
Stackalytics according to the implementation through 
https://review.openstack.org/#/c/288871/ .


For the perspective on Stackalytics <-> the list of projects, another 
possible solution would be to create "openstack-org" project in Zanata,
migrate edge-computing & container whitepaper into "openstack-org" 
project with different version names, ane

adding "openstack-org" project in Stackalytics for consistency.


With many thanks,

/Ian

Frank Kloeker wrote on 8/7/2018 4:49 PM:
Many thanks, Jimmy! At last I draw your attention to Stackalytics. 
Translation metrics for whitepapers not counted there. Maybe you have 
an advice for https://review.openstack.org/#/c/588965/


kind regards

Frank

Am 2018-08-06 21:07, schrieb Jimmy McArthur:

A heads up that the Translators are now listed at the bottom of the
page as well, along with the rest of the paper contributors:

https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center?lang=ja_JP 



Cheers!
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

thanks for announcement. Great stuff! It looks really great and 
it's easy to navigate. I think a special thanks goes to Sebastian 
for designing the pages. One small remark: have you tried 
text-align: justify? I think it would be a little bit more 
readable, like a science paper (German word is: Ordnung)
I put the projects again on the frontpage of the translation 
platform, so we'll get more translations shortly.


kind regards

Frank

Am 2018-08-02 21:07, schrieb Jimmy McArthur:

The Edge and Containers translations are now live.  As new
translations become available, we will add them to the page.

https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at 
this

time, so I've left the PDF download up on that page.

Thanks everyone and please let me know if you have questions or 
concerns!


Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update 
this thread when we do.


Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem 
with XML-Parsing of the term AT Don't know how to escape 
this. Maybe you will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot 
missed
some parts of the original paper (subsections of the paper) 
apologizes

on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  
wrote:



Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center 


[1]

paper version  are only in container whitepaper:


https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack 


[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the 
Zanata API:


https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing 


[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 


[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-07 Thread Ian Y. Choi

Hello Frank,

I did not notice the list of project but just from the perspective of 
translation metrics in Stackalytics and Zanata,
whitepaper translation contribution is retrieved from Zanata to 
Stackalytics according to the implementation through 
https://review.openstack.org/#/c/288871/ .


For the perspective on Stackalytics <-> the list of projects, another 
possible solution would be to create "openstack-org" project in Zanata,
migrate edge-computing & container whitepaper into "openstack-org" 
project with different version names, ane

adding "openstack-org" project in Stackalytics for consistency.


With many thanks,

/Ian

Frank Kloeker wrote on 8/7/2018 4:49 PM:
Many thanks, Jimmy! At last I draw your attention to Stackalytics. 
Translation metrics for whitepapers not counted there. Maybe you have 
an advice for https://review.openstack.org/#/c/588965/


kind regards

Frank

Am 2018-08-06 21:07, schrieb Jimmy McArthur:

A heads up that the Translators are now listed at the bottom of the
page as well, along with the rest of the paper contributors:

https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center?lang=ja_JP 



Cheers!
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

thanks for announcement. Great stuff! It looks really great and it's 
easy to navigate. I think a special thanks goes to Sebastian for 
designing the pages. One small remark: have you tried text-align: 
justify? I think it would be a little bit more readable, like a 
science paper (German word is: Ordnung)
I put the projects again on the frontpage of the translation 
platform, so we'll get more translations shortly.


kind regards

Frank

Am 2018-08-02 21:07, schrieb Jimmy McArthur:

The Edge and Containers translations are now live.  As new
translations become available, we will add them to the page.

https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at this
time, so I've left the PDF download up on that page.

Thanks everyone and please let me know if you have questions or 
concerns!


Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update this 
thread when we do.


Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. 
Maybe you will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot 
missed
some parts of the original paper (subsections of the paper) 
apologizes

on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  
wrote:



Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center 


[1]

paper version  are only in container whitepaper:


https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack 


[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata 
API:


https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing 


[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 


[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could 
prevent

that additional 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-07 Thread Frank Kloeker
Many thanks, Jimmy! At last I draw your attention to Stackalytics. 
Translation metrics for whitepapers not counted there. Maybe you have an 
advice for https://review.openstack.org/#/c/588965/


kind regards

Frank

Am 2018-08-06 21:07, schrieb Jimmy McArthur:

A heads up that the Translators are now listed at the bottom of the
page as well, along with the rest of the paper contributors:

https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center?lang=ja_JP

Cheers!
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

thanks for announcement. Great stuff! It looks really great and it's 
easy to navigate. I think a special thanks goes to Sebastian for 
designing the pages. One small remark: have you tried text-align: 
justify? I think it would be a little bit more readable, like a 
science paper (German word is: Ordnung)
I put the projects again on the frontpage of the translation platform, 
so we'll get more translations shortly.


kind regards

Frank

Am 2018-08-02 21:07, schrieb Jimmy McArthur:

The Edge and Containers translations are now live.  As new
translations become available, we will add them to the page.

https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at 
this

time, so I've left the PDF download up on that page.

Thanks everyone and please let me know if you have questions or 
concerns!


Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update this 
thread when we do.


Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe 
you will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot 
missed
some parts of the original paper (subsections of the paper) 
apologizes

on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  
wrote:



Hi Jimmy,

from the GUI I'll get this link:


https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

[1]

paper version  are only in container whitepaper:



https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata 
API:



https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:


https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could 
prevent

that additional design resource cost.
On the other hand, the source strings of edge computing 
whitepaper

which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in 
the

same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work 
on
the RST-based translation.  At the moment, it's just not usable 
for

the reasons 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-06 Thread Jimmy McArthur
A heads up that the Translators are now listed at the bottom of the page 
as well, along with the rest of the paper contributors:


https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center?lang=ja_JP

Cheers!
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

thanks for announcement. Great stuff! It looks really great and it's 
easy to navigate. I think a special thanks goes to Sebastian for 
designing the pages. One small remark: have you tried text-align: 
justify? I think it would be a little bit more readable, like a 
science paper (German word is: Ordnung)
I put the projects again on the frontpage of the translation platform, 
so we'll get more translations shortly.


kind regards

Frank

Am 2018-08-02 21:07, schrieb Jimmy McArthur:

The Edge and Containers translations are now live.  As new
translations become available, we will add them to the page.

https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at this
time, so I've left the PDF download up on that page.

Thanks everyone and please let me know if you have questions or 
concerns!


Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update this 
thread when we do.


Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe 
you will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) 
apologizes

on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  
wrote:



Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center 


[1]

paper version  are only in container whitepaper:


https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack 


[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata API:

https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing 


[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 


[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation.  At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-03 Thread Frank Kloeker

Hi Jimmy,

thanks for announcement. Great stuff! It looks really great and it's 
easy to navigate. I think a special thanks goes to Sebastian for 
designing the pages. One small remark: have you tried text-align: 
justify? I think it would be a little bit more readable, like a science 
paper (German word is: Ordnung)
I put the projects again on the frontpage of the translation platform, 
so we'll get more translations shortly.


kind regards

Frank

Am 2018-08-02 21:07, schrieb Jimmy McArthur:

The Edge and Containers translations are now live.  As new
translations become available, we will add them to the page.

https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at this
time, so I've left the PDF download up on that page.

Thanks everyone and please let me know if you have questions or 
concerns!


Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update this 
thread when we do.


Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe 
you will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) 
apologizes

on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  
wrote:



Hi Jimmy,

from the GUI I'll get this link:


https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

[1]

paper version  are only in container whitepaper:



https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata 
API:



https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:


https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could 
prevent

that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in 
the

same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation.  At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-02 Thread Jimmy McArthur
The Edge and Containers translations are now live.  As new translations 
become available, we will add them to the page.


https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at this 
time, so I've left the PDF download up on that page.


Thanks everyone and please let me know if you have questions or concerns!

Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update this 
thread when we do.


Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe 
you will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) apologizes
on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  wrote:


Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center 


[1]

paper version  are only in container whitepaper:


https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack 


[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata API:

https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing 


[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 


[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation.  At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html [5] describes
well how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version
of the OpenStack website


Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-02 Thread Jimmy McArthur

Frank,

We expect to have these papers up this afternoon. I'll update this 
thread when we do.


Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe you 
will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) apologizes
on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  wrote:


Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center 


[1]

paper version  are only in container whitepaper:


https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack 


[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata API:

https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing 


[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 


[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation.  At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html [5] describes
well how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version
of the OpenStack website

(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md 


[6]).  However, we have to manually ingest the po files as they are
completed and then push them out to production, so that wouldn't do
much to help with your local build.  I'm open to suggestions on how
we can make this process easier for the i18n team.

Thank you,
Jimmy

With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:
Frank,

I'm sorry to hear about the displeasure around 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-02 Thread Sebastian Marcet
Hello Ian, due the nature of the pot file format and mechanic
we cant add the translators as msgid entries bc will only exist on the
corresponding po file per lang
said that , i think that we could create a solution using both [1] and [2]
that said
* adding "TRANSLATORS" msgid on pot file, so i could get that string per
lang
* adding translators names as stated on [2] as po file metadata so i could
parse and display per language


regards

On Wed, Aug 1, 2018 at 11:03 PM, Ian Y. Choi  wrote:

> Hello Sebastian,
>
> Korean has also currently 100% translation now.
> About two weeks ago, there were a discussion how to include the list of
> translators per translated document.
>
> My proposal is mentioned in [1] - do you think it is a good idea and it is
> under implementation,
> or parsing the name of translators in header lines on po files (e.g., four
> lines on [2]) would be better idea?
>
>
> With many thanks,
>
> /Ian
>
> [1] http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%
> 23openstack-i18n.2018-07-19.log.html#t2018-07-19T15:09:46
> [2] http://git.openstack.org/cgit/openstack/i18n/tree/doc/source
> /locale/de/LC_MESSAGES/doc.po#n1
>
>
> Frank Kloeker wrote on 7/31/2018 6:39 PM:
>
>> Hi Sebastian,
>>
>> okay, it's translated now. In Edge whitepaper is the problem with
>> XML-Parsing of the term AT Don't know how to escape this. Maybe you will
>> see the warning during import too.
>>
>> kind regards
>>
>> Frank
>>
>> Am 2018-07-30 20:09, schrieb Sebastian Marcet:
>>
>>> Hi Frank,
>>> i was double checking pot file and realized that original pot missed
>>> some parts of the original paper (subsections of the paper) apologizes
>>> on that
>>> i just re uploaded an updated pot file with missing subsections
>>>
>>> regards
>>>
>>> On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  wrote:
>>>
>>> Hi Jimmy,

 from the GUI I'll get this link:

 https://translate.openstack.org/rest/file/translation/edge-
>>> computing/pot-translation/de/po?docId=cloud-edge-computing-
>>> beyond-the-data-center
>>>
 [1]

 paper version  are only in container whitepaper:


 https://translate.openstack.org/rest/file/translation/levera
>>> ging-containers-openstack/paper/de/po?docId=leveraging-
>>> containers-and-openstack
>>>
 [2]

 In general there is no group named papers

 kind regards

 Frank

 Am 2018-07-30 17:06, schrieb Jimmy McArthur:
 Frank,

 We're getting a 404 when looking for the pot file on the Zanata API:

 https://translate.openstack.org/rest/file/translation/papers
>>> /papers/de/po?docId=edge-computing
>>>
 [3]

 As a result, we can't pull the po files.  Any idea what might be
 happening?

 Seeing the same thing with both papers...

 Thank you,
 Jimmy

 Frank Kloeker wrote:
 Hi Jimmy,

 Korean and German version are now done on the new format. Can you
 check publishing?

 thx

 Frank

 Am 2018-07-19 16:47, schrieb Jimmy McArthur:
 Hi all -

 Follow up on the Edge paper specifically:

 https://translate.openstack.org/iteration/view/edge-computin
>>> g/pot-translation/documents?dswid=-3192
>>>
 [4] This is now available. As I mentioned on IRC this morning, it
 should
 be VERY close to the PDF.  Probably just needs a quick review.

 Let me know if I can assist with anything.

 Thank you to i18n team for all of your help!!!

 Cheers,
 Jimmy

 Jimmy McArthur wrote:
 Ian raises some great points :) I'll try to address below...

 Ian Y. Choi wrote:
 Hello,

 When I saw overall translation source strings on container
 whitepaper, I would infer that new edge computing whitepaper
 source strings would include HTML markup tags.
 One of the things I discussed with Ian and Frank in Vancouver is
 the expense of recreating PDFs with new translations.  It's
 prohibitively expensive for the Foundation as it requires design
 resources which we just don't have.  As a result, we created the
 Containers whitepaper in HTML, so that it could be easily updated
 w/o working with outside design contractors.  I indicated that we
 would also be moving the Edge paper to HTML so that we could prevent
 that additional design resource cost.
 On the other hand, the source strings of edge computing whitepaper
 which I18n team previously translated do not include HTML markup
 tags, since the source strings are based on just text format.
 The version that Akihiro put together was based on the Edge PDF,
 which we unfortunately didn't have the resources to implement in the
 same format.

 I really appreciate Akihiro's work on RST-based support on
 publishing translated edge computing whitepapers, since
 translators do not have to re-translate all the strings.
 I would like to second this. It 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-01 Thread Ian Y. Choi

Hello Sebastian,

Korean has also currently 100% translation now.
About two weeks ago, there were a discussion how to include the list of 
translators per translated document.


My proposal is mentioned in [1] - do you think it is a good idea and it 
is under implementation,
or parsing the name of translators in header lines on po files (e.g., 
four lines on [2]) would be better idea?



With many thanks,

/Ian

[1] 
http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.2018-07-19.log.html#t2018-07-19T15:09:46
[2] 
http://git.openstack.org/cgit/openstack/i18n/tree/doc/source/locale/de/LC_MESSAGES/doc.po#n1


Frank Kloeker wrote on 7/31/2018 6:39 PM:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe you 
will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) apologizes
on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  wrote:


Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center 


[1]

paper version  are only in container whitepaper:


https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack 


[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata API:

https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing 


[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 


[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation.  At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html [5] describes
well how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-31 Thread Frank Kloeker

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe you 
will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) apologizes
on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  wrote:


Hi Jimmy,

from the GUI I'll get this link:


https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

[1]

paper version  are only in container whitepaper:



https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata API:


https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:


https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation.  At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html [5] describes
well how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version
of the OpenStack website


(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md

[6]).  However, we have to manually ingest the po files as they are
completed and then push them out to production, so that wouldn't do
much to help with your local build.  I'm open to suggestions on how
we can make this process easier for the i18n team.

Thank you,
Jimmy

With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:
Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As
mentioned in a prior thread, the RST format that Akihiro worked did
not work with the  Zanata process that we have been 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-30 Thread Sebastian Marcet
Hi Frank,
i was double checking pot file and realized that original pot missed some
parts of the original paper (subsections of the paper) apologizes on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  wrote:

> Hi Jimmy,
>
> from the GUI I'll get this link:
> https://translate.openstack.org/rest/file/translation/edge-
> computing/pot-translation/de/po?docId=cloud-edge-computing-
> beyond-the-data-center
>
> paper version  are only in container whitepaper:
>
> https://translate.openstack.org/rest/file/translation/levera
> ging-containers-openstack/paper/de/po?docId=leveraging-
> containers-and-openstack
>
> In general there is no group named papers
>
> kind regards
>
> Frank
>
>
> Am 2018-07-30 17:06, schrieb Jimmy McArthur:
>
>> Frank,
>>
>> We're getting a 404 when looking for the pot file on the Zanata API:
>> https://translate.openstack.org/rest/file/translation/papers
>> /papers/de/po?docId=edge-computing
>>
>> As a result, we can't pull the po files.  Any idea what might be
>> happening?
>>
>> Seeing the same thing with both papers...
>>
>> Thank you,
>> Jimmy
>>
>> Frank Kloeker wrote:
>>
>>> Hi Jimmy,
>>>
>>> Korean and German version are now done on the new format. Can you check
>>> publishing?
>>>
>>> thx
>>>
>>> Frank
>>>
>>> Am 2018-07-19 16:47, schrieb Jimmy McArthur:
>>>
 Hi all -

 Follow up on the Edge paper specifically:
 https://translate.openstack.org/iteration/view/edge-computin
 g/pot-translation/documents?dswid=-3192 This is now available. As I
 mentioned on IRC this morning, it should
 be VERY close to the PDF.  Probably just needs a quick review.

 Let me know if I can assist with anything.

 Thank you to i18n team for all of your help!!!

 Cheers,
 Jimmy

 Jimmy McArthur wrote:

> Ian raises some great points :) I'll try to address below...
>
> Ian Y. Choi wrote:
>
>> Hello,
>>
>> When I saw overall translation source strings on container
>> whitepaper, I would infer that new edge computing whitepaper
>> source strings would include HTML markup tags.
>>
> One of the things I discussed with Ian and Frank in Vancouver is the
> expense of recreating PDFs with new translations.  It's prohibitively
> expensive for the Foundation as it requires design resources which we just
> don't have.  As a result, we created the Containers whitepaper in HTML, so
> that it could be easily updated w/o working with outside design
> contractors.  I indicated that we would also be moving the Edge paper to
> HTML so that we could prevent that additional design resource cost.
>
>> On the other hand, the source strings of edge computing whitepaper
>> which I18n team previously translated do not include HTML markup
>> tags, since the source strings are based on just text format.
>>
> The version that Akihiro put together was based on the Edge PDF, which
> we unfortunately didn't have the resources to implement in the same 
> format.
>
>>
>> I really appreciate Akihiro's work on RST-based support on publishing
>> translated edge computing whitepapers, since
>> translators do not have to re-translate all the strings.
>>
> I would like to second this. It took a lot of initiative to work on
> the RST-based translation.  At the moment, it's just not usable for the
> reasons mentioned above.
>
>> On the other hand, it seems that I18n team needs to investigate on
>> translating similar strings of HTML-based edge computing whitepaper
>> source strings, which would discourage translators.
>>
> Can you expand on this? I'm not entirely clear on why the HTML based
> translation is more difficult.
>
>>
>> That's my point of view on translating edge computing whitepaper.
>>
>> For translating container whitepaper, I want to further ask the
>> followings since *I18n-based tools*
>> would mean for translators that translators can test and publish
>> translated whitepapers locally:
>>
>> - How to build translated container whitepaper using original
>> Silverstripe-based repository?
>>   https://docs.openstack.org/i18n/latest/tools.html describes well
>> how to build translated artifacts for RST-based OpenStack repositories
>>   but I could not find the way how to build translated container
>> whitepaper with translated resources on Zanata.
>>
> This is a little tricky.  It's possible to set up a local version of
> the OpenStack website (https://github.com/OpenStackw
> eb/openstack-org/blob/master/installation.md).  However, we have to
> manually ingest the po files as they are completed and then push them out
> to production, so that wouldn't do much to help with your local build.  
> I'm
> open to suggestions on how we can make 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-30 Thread Frank Kloeker

Hi Jimmy,

from the GUI I'll get this link:
https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

paper version  are only in container whitepaper:

https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:

Frank,

We're getting a 404 when looking for the pot file on the Zanata API:
https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

As a result, we can't pull the po files.  Any idea what might be 
happening?


Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

Korean and German version are now done on the new format. Can you 
check publishing?


thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:

Hi all -

Follow up on the Edge paper specifically:
https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 
This is now available. As I mentioned on IRC this morning, it should

be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:

Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:

Hello,

When I saw overall translation source strings on container 
whitepaper, I would infer that new edge computing whitepaper

source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is the 
expense of recreating PDFs with new translations.  It's 
prohibitively expensive for the Foundation as it requires design 
resources which we just don't have.  As a result, we created the 
Containers whitepaper in HTML, so that it could be easily updated 
w/o working with outside design contractors.  I indicated that we 
would also be moving the Edge paper to HTML so that we could prevent 
that additional design resource cost.

On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup 
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF, 
which we unfortunately didn't have the resources to implement in the 
same format.


I really appreciate Akihiro's work on RST-based support on 
publishing translated edge computing whitepapers, since

translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on 
the RST-based translation.  At the moment, it's just not usable for 
the reasons mentioned above.

On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper 
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML based 
translation is more difficult.


That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the 
followings since *I18n-based tools*
would mean for translators that translators can test and publish 
translated whitepapers locally:


- How to build translated container whitepaper using original 
Silverstripe-based repository?
  https://docs.openstack.org/i18n/latest/tools.html describes well 
how to build translated artifacts for RST-based OpenStack 
repositories
  but I could not find the way how to build translated container 
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version of 
the OpenStack website 
(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md). 
 However, we have to manually ingest the po files as they are 
completed and then push them out to production, so that wouldn't do 
much to help with your local build.  I'm open to suggestions on how 
we can make this process easier for the i18n team.


Thank you,
Jimmy



With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As 
mentioned in a prior thread, the RST format that Akihiro worked 
did not work with the  Zanata process that we have been using with 
our CMS.  Additionally, the existing EDGE page is a PDF, so we had 
to build a new template to work with the new HTML whitepaper 
layout we created for the Containers paper. I outlined this in the 
thread " [OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge 
Computing Whitepaper Translation" on 6/25/18 and mentioned we 
would be ready with the template around 7/13.


We completed the work on the new whitepaper template and then put 
out the pot files on Zanata so we can get the po language files 
back. If this 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-30 Thread Jimmy McArthur

Frank,

We're getting a 404 when looking for the pot file on the Zanata API: 
https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing


As a result, we can't pull the po files.  Any idea what might be happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

Korean and German version are now done on the new format. Can you 
check publishing?


thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:

Hi all -

Follow up on the Edge paper specifically:
https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 



This is now available. As I mentioned on IRC this morning, it should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:

Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:

Hello,

When I saw overall translation source strings on container 
whitepaper, I would infer that new edge computing whitepaper

source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is the 
expense of recreating PDFs with new translations.  It's 
prohibitively expensive for the Foundation as it requires design 
resources which we just don't have.  As a result, we created the 
Containers whitepaper in HTML, so that it could be easily updated 
w/o working with outside design contractors.  I indicated that we 
would also be moving the Edge paper to HTML so that we could prevent 
that additional design resource cost.

On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup 
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF, 
which we unfortunately didn't have the resources to implement in the 
same format.


I really appreciate Akihiro's work on RST-based support on 
publishing translated edge computing whitepapers, since

translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on 
the RST-based translation.  At the moment, it's just not usable for 
the reasons mentioned above.

On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper 
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML based 
translation is more difficult.


That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the 
followings since *I18n-based tools*
would mean for translators that translators can test and publish 
translated whitepapers locally:


- How to build translated container whitepaper using original 
Silverstripe-based repository?
  https://docs.openstack.org/i18n/latest/tools.html describes well 
how to build translated artifacts for RST-based OpenStack repositories
  but I could not find the way how to build translated container 
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version of 
the OpenStack website 
(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md). 
 However, we have to manually ingest the po files as they are 
completed and then push them out to production, so that wouldn't do 
much to help with your local build.  I'm open to suggestions on how 
we can make this process easier for the i18n team.


Thank you,
Jimmy



With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As 
mentioned in a prior thread, the RST format that Akihiro worked 
did not work with the  Zanata process that we have been using with 
our CMS.  Additionally, the existing EDGE page is a PDF, so we had 
to build a new template to work with the new HTML whitepaper 
layout we created for the Containers paper. I outlined this in the 
thread " [OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge 
Computing Whitepaper Translation" on 6/25/18 and mentioned we 
would be ready with the template around 7/13.


We completed the work on the new whitepaper template and then put 
out the pot files on Zanata so we can get the po language files 
back. If this process is too cumbersome for the translation team, 
I'm open to discussion, but right now our entire translation 
process is based on the official OpenStack Docs translation 
process outlined by the i18n team: 
https://docs.openstack.org/i18n/latest/en_GB/tools.html


Again, I realize Akihiro put in some work on his own proposing the 
new translation type. If the i18n team is moving to this format 
instead, we can work on redoing our process.


Please let me know if I can clarify 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-30 Thread Frank Kloeker

Hi Jimmy,

Korean and German version are now done on the new format. Can you check 
publishing?


thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:

Hi all -

Follow up on the Edge paper specifically:
https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

This is now available. As I mentioned on IRC this morning, it should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:

Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:

Hello,

When I saw overall translation source strings on container 
whitepaper, I would infer that new edge computing whitepaper

source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is the 
expense of recreating PDFs with new translations.  It's prohibitively 
expensive for the Foundation as it requires design resources which we 
just don't have.  As a result, we created the Containers whitepaper in 
HTML, so that it could be easily updated w/o working with outside 
design contractors.  I indicated that we would also be moving the Edge 
paper to HTML so that we could prevent that additional design resource 
cost.

On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup 
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF, which 
we unfortunately didn't have the resources to implement in the same 
format.


I really appreciate Akihiro's work on RST-based support on publishing 
translated edge computing whitepapers, since

translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on 
the RST-based translation.  At the moment, it's just not usable for 
the reasons mentioned above.

On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper 
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML based 
translation is more difficult.


That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the 
followings since *I18n-based tools*
would mean for translators that translators can test and publish 
translated whitepapers locally:


- How to build translated container whitepaper using original 
Silverstripe-based repository?
  https://docs.openstack.org/i18n/latest/tools.html describes well 
how to build translated artifacts for RST-based OpenStack 
repositories
  but I could not find the way how to build translated container 
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version of 
the OpenStack website 
(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md). 
 However, we have to manually ingest the po files as they are 
completed and then push them out to production, so that wouldn't do 
much to help with your local build.  I'm open to suggestions on how we 
can make this process easier for the i18n team.


Thank you,
Jimmy



With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As 
mentioned in a prior thread, the RST format that Akihiro worked did 
not work with the  Zanata process that we have been using with our 
CMS.  Additionally, the existing EDGE page is a PDF, so we had to 
build a new template to work with the new HTML whitepaper layout we 
created for the Containers paper. I outlined this in the thread " 
[OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing 
Whitepaper Translation" on 6/25/18 and mentioned we would be ready 
with the template around 7/13.


We completed the work on the new whitepaper template and then put 
out the pot files on Zanata so we can get the po language files 
back. If this process is too cumbersome for the translation team, 
I'm open to discussion, but right now our entire translation process 
is based on the official OpenStack Docs translation process outlined 
by the i18n team: 
https://docs.openstack.org/i18n/latest/en_GB/tools.html


Again, I realize Akihiro put in some work on his own proposing the 
new translation type. If the i18n team is moving to this format 
instead, we can work on redoing our process.


Please let me know if I can clarify further.

Thanks,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

permission was added for you and Sebastian. The Container 
Whitepaper is on the Zanata frontpage now. But we removed Edge 
Computing whitepaper last week because there is a kind of 
displeasure in the team since the results of translation are still 
not published beside Chinese 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-19 Thread Jimmy McArthur

Hi all -

Follow up on the Edge paper specifically: 
https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192


This is now available. As I mentioned on IRC this morning, it should be 
VERY close to the PDF.  Probably just needs a quick review.


Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:

Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:

Hello,

When I saw overall translation source strings on container 
whitepaper, I would infer that new edge computing whitepaper

source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is the 
expense of recreating PDFs with new translations.  It's prohibitively 
expensive for the Foundation as it requires design resources which we 
just don't have.  As a result, we created the Containers whitepaper in 
HTML, so that it could be easily updated w/o working with outside 
design contractors.  I indicated that we would also be moving the Edge 
paper to HTML so that we could prevent that additional design resource 
cost.

On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup 
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF, which 
we unfortunately didn't have the resources to implement in the same 
format.


I really appreciate Akihiro's work on RST-based support on publishing 
translated edge computing whitepapers, since
translators do not have to re-translate all the strings. 
I would like to second this. It took a lot of initiative to work on 
the RST-based translation.  At the moment, it's just not usable for 
the reasons mentioned above.

On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper 
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML based 
translation is more difficult.


That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the 
followings since *I18n-based tools*
would mean for translators that translators can test and publish 
translated whitepapers locally:


- How to build translated container whitepaper using original 
Silverstripe-based repository?
  https://docs.openstack.org/i18n/latest/tools.html describes well 
how to build translated artifacts for RST-based OpenStack repositories
  but I could not find the way how to build translated container 
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version of 
the OpenStack website 
(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md).  
However, we have to manually ingest the po files as they are completed 
and then push them out to production, so that wouldn't do much to help 
with your local build.  I'm open to suggestions on how we can make 
this process easier for the i18n team.


Thank you,
Jimmy



With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As 
mentioned in a prior thread, the RST format that Akihiro worked did 
not work with the  Zanata process that we have been using with our 
CMS.  Additionally, the existing EDGE page is a PDF, so we had to 
build a new template to work with the new HTML whitepaper layout we 
created for the Containers paper. I outlined this in the thread " 
[OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing 
Whitepaper Translation" on 6/25/18 and mentioned we would be ready 
with the template around 7/13.


We completed the work on the new whitepaper template and then put 
out the pot files on Zanata so we can get the po language files 
back. If this process is too cumbersome for the translation team, 
I'm open to discussion, but right now our entire translation process 
is based on the official OpenStack Docs translation process outlined 
by the i18n team: 
https://docs.openstack.org/i18n/latest/en_GB/tools.html


Again, I realize Akihiro put in some work on his own proposing the 
new translation type. If the i18n team is moving to this format 
instead, we can work on redoing our process.


Please let me know if I can clarify further.

Thanks,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

permission was added for you and Sebastian. The Container 
Whitepaper is on the Zanata frontpage now. But we removed Edge 
Computing whitepaper last week because there is a kind of 
displeasure in the team since the results of translation are still 
not published beside Chinese version. It would be nice if we have a 
commitment from the Foundation that results are published in a 
specific timeframe. This includes your 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-17 Thread Jimmy McArthur

Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:

Hello,

When I saw overall translation source strings on container whitepaper, 
I would infer that new edge computing whitepaper

source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is the 
expense of recreating PDFs with new translations.  It's prohibitively 
expensive for the Foundation as it requires design resources which we 
just don't have.  As a result, we created the Containers whitepaper in 
HTML, so that it could be easily updated w/o working with outside design 
contractors.  I indicated that we would also be moving the Edge paper to 
HTML so that we could prevent that additional design resource cost.

On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup tags, 
since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF, which 
we unfortunately didn't have the resources to implement in the same format.


I really appreciate Akihiro's work on RST-based support on publishing 
translated edge computing whitepapers, since
translators do not have to re-translate all the strings. 
I would like to second this. It took a lot of initiative to work on the 
RST-based translation.  At the moment, it's just not usable for the 
reasons mentioned above.

On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper 
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML based 
translation is more difficult.


That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the 
followings since *I18n-based tools*
would mean for translators that translators can test and publish 
translated whitepapers locally:


- How to build translated container whitepaper using original 
Silverstripe-based repository?
  https://docs.openstack.org/i18n/latest/tools.html describes well how 
to build translated artifacts for RST-based OpenStack repositories
  but I could not find the way how to build translated container 
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version of the 
OpenStack website 
(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md).  
However, we have to manually ingest the po files as they are completed 
and then push them out to production, so that wouldn't do much to help 
with your local build.  I'm open to suggestions on how we can make this 
process easier for the i18n team.


Thank you,
Jimmy



With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As 
mentioned in a prior thread, the RST format that Akihiro worked did 
not work with the  Zanata process that we have been using with our 
CMS.  Additionally, the existing EDGE page is a PDF, so we had to 
build a new template to work with the new HTML whitepaper layout we 
created for the Containers paper. I outlined this in the thread " 
[OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing 
Whitepaper Translation" on 6/25/18 and mentioned we would be ready 
with the template around 7/13.


We completed the work on the new whitepaper template and then put out 
the pot files on Zanata so we can get the po language files back. If 
this process is too cumbersome for the translation team, I'm open to 
discussion, but right now our entire translation process is based on 
the official OpenStack Docs translation process outlined by the i18n 
team: https://docs.openstack.org/i18n/latest/en_GB/tools.html


Again, I realize Akihiro put in some work on his own proposing the 
new translation type. If the i18n team is moving to this format 
instead, we can work on redoing our process.


Please let me know if I can clarify further.

Thanks,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

permission was added for you and Sebastian. The Container Whitepaper 
is on the Zanata frontpage now. But we removed Edge Computing 
whitepaper last week because there is a kind of displeasure in the 
team since the results of translation are still not published beside 
Chinese version. It would be nice if we have a commitment from the 
Foundation that results are published in a specific timeframe. This 
includes your requirements until the translation should be available.


thx Frank

Am 2018-07-16 17:26, schrieb Jimmy McArthur:

Sorry, I should have also added... we additionally need permissions so
that we can add the a new version of the pot file to this project:
https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835 



Thanks!
Jimmy



Jimmy McArthur wrote:

Hi all -

We have both of the current whitepapers up and 

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-17 Thread Ian Y. Choi

Hello,

When I saw overall translation source strings on container whitepaper, I 
would infer that new edge computing whitepaper
source strings would include HTML markup tags. On the other hand, the 
source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup tags, 
since the source strings are based on just text format.


I really appreciate Akihiro's work on RST-based support on publishing 
translated edge computing whitepapers, since
translators do not have to re-translate all the strings. On the other 
hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper 
source strings, which would discourage translators.


That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the 
followings since *I18n-based tools*
would mean for translators that translators can test and publish 
translated whitepapers locally:


- How to build translated container whitepaper using original 
Silverstripe-based repository?
  https://docs.openstack.org/i18n/latest/tools.html describes well how 
to build translated artifacts for RST-based OpenStack repositories
  but I could not find the way how to build translated container 
whitepaper with translated resources on Zanata.



With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As 
mentioned in a prior thread, the RST format that Akihiro worked did 
not work with the  Zanata process that we have been using with our 
CMS.  Additionally, the existing EDGE page is a PDF, so we had to 
build a new template to work with the new HTML whitepaper layout we 
created for the Containers paper. I outlined this in the thread " 
[OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing 
Whitepaper Translation" on 6/25/18 and mentioned we would be ready 
with the template around 7/13.


We completed the work on the new whitepaper template and then put out 
the pot files on Zanata so we can get the po language files back. If 
this process is too cumbersome for the translation team, I'm open to 
discussion, but right now our entire translation process is based on 
the official OpenStack Docs translation process outlined by the i18n 
team: https://docs.openstack.org/i18n/latest/en_GB/tools.html


Again, I realize Akihiro put in some work on his own proposing the new 
translation type. If the i18n team is moving to this format instead, 
we can work on redoing our process.


Please let me know if I can clarify further.

Thanks,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

permission was added for you and Sebastian. The Container Whitepaper 
is on the Zanata frontpage now. But we removed Edge Computing 
whitepaper last week because there is a kind of displeasure in the 
team since the results of translation are still not published beside 
Chinese version. It would be nice if we have a commitment from the 
Foundation that results are published in a specific timeframe. This 
includes your requirements until the translation should be available.


thx Frank

Am 2018-07-16 17:26, schrieb Jimmy McArthur:

Sorry, I should have also added... we additionally need permissions so
that we can add the a new version of the pot file to this project:
https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835 



Thanks!
Jimmy



Jimmy McArthur wrote:

Hi all -

We have both of the current whitepapers up and available for 
translation.  Can we promote these on the Zanata homepage?


https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684 
https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684 
Thanks all!

Jimmy



__ 


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__ 


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-17 Thread Jimmy McArthur

Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As 
mentioned in a prior thread, the RST format that Akihiro worked did not 
work with the  Zanata process that we have been using with our CMS.  
Additionally, the existing EDGE page is a PDF, so we had to build a new 
template to work with the new HTML whitepaper layout we created for the 
Containers paper. I outlined this in the thread " [OpenStack-I18n] 
[Edge-computing] [Openstack-sigs] Edge Computing Whitepaper Translation" 
on 6/25/18 and mentioned we would be ready with the template around 7/13.


We completed the work on the new whitepaper template and then put out 
the pot files on Zanata so we can get the po language files back. If 
this process is too cumbersome for the translation team, I'm open to 
discussion, but right now our entire translation process is based on the 
official OpenStack Docs translation process outlined by the i18n team: 
https://docs.openstack.org/i18n/latest/en_GB/tools.html


Again, I realize Akihiro put in some work on his own proposing the new 
translation type. If the i18n team is moving to this format instead, we 
can work on redoing our process.


Please let me know if I can clarify further.

Thanks,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

permission was added for you and Sebastian. The Container Whitepaper 
is on the Zanata frontpage now. But we removed Edge Computing 
whitepaper last week because there is a kind of displeasure in the 
team since the results of translation are still not published beside 
Chinese version. It would be nice if we have a commitment from the 
Foundation that results are published in a specific timeframe. This 
includes your requirements until the translation should be available.


thx Frank

Am 2018-07-16 17:26, schrieb Jimmy McArthur:

Sorry, I should have also added... we additionally need permissions so
that we can add the a new version of the pot file to this project:
https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835 



Thanks!
Jimmy



Jimmy McArthur wrote:

Hi all -

We have both of the current whitepapers up and available for 
translation.  Can we promote these on the Zanata homepage?


https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684 
https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684 
Thanks all!

Jimmy



__ 


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-17 Thread Frank Kloeker

Hi Jimmy,

permission was added for you and Sebastian. The Container Whitepaper is 
on the Zanata frontpage now. But we removed Edge Computing whitepaper 
last week because there is a kind of displeasure in the team since the 
results of translation are still not published beside Chinese version. 
It would be nice if we have a commitment from the Foundation that 
results are published in a specific timeframe. This includes your 
requirements until the translation should be available.


thx Frank

Am 2018-07-16 17:26, schrieb Jimmy McArthur:

Sorry, I should have also added... we additionally need permissions so
that we can add the a new version of the pot file to this project:
https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835

Thanks!
Jimmy



Jimmy McArthur wrote:

Hi all -

We have both of the current whitepapers up and available for 
translation.  Can we promote these on the Zanata homepage?


https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684 
https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684 
Thanks all!

Jimmy



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-16 Thread Jimmy McArthur



Jimmy McArthur wrote:



Akihiro Motoki wrote:

Jimmy,

Does it mean translation **publishing** is ready now?

In the first translation of the edge computing whitepaper, 
translation publishing was completely a manual process and it takes 
too long.
The initial version was a volunteer effort, but the Foundation wasn't 
aware it was taking place until after it was all done.  Our efforts 
are aligned around working through standard Zanata publishing processes.
Also, FTR, I believe it should be easy enough to take those initial 
manual translations and place them into the po files once we add the pot 
file to the project.
If translation publishing support is not ready, it is a bit 
discouraging from translator perspective.
We translators would like to have some automated way to publish 
translated versions of documents
and it allows translators to improve and/or fix translations after 
the initial translation.
Translation publishing is now available.  We just need permissions to 
add the pot file to the project. Moving forward, the process will be 
automated through Zanata in the same way we do the user survey and 
other features.


I propose an idea of using RST file for the edge computing whitepaper 
after the Vancouver summit.
Yes, we're following the standard publishing requirements outlined 
here: https://docs.openstack.org/i18n/latest/en_GB/tools.html
Ildiko said it is being discussed in the edge computing team and the 
foundation but I haven't heard nothing since then.
Or can the foundation publish translations more quickly even though 
the current publishing process is not changed.
If not, I cannot believe this is the right timing to promote 
whitepaper translations.




Thanks,
Akihiro


2018年7月17日(火) 0:27 Jimmy McArthur >:


Sorry, I should have also added... we additionally need
permissions so
that we can add the a new version of the pot file to this project:

https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835

Thanks!
Jimmy



Jimmy McArthur wrote:
> Hi all -
>
> We have both of the current whitepapers up and available for
> translation.  Can we promote these on the Zanata homepage?
>
>

https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684

>
>

https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684

>
>
> Thanks all!
> Jimmy


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-16 Thread Jimmy McArthur



Akihiro Motoki wrote:

Jimmy,

Does it mean translation **publishing** is ready now?

In the first translation of the edge computing whitepaper, translation 
publishing was completely a manual process and it takes too long.
The initial version was a volunteer effort, but the Foundation wasn't 
aware it was taking place until after it was all done.  Our efforts are 
aligned around working through standard Zanata publishing processes.
If translation publishing support is not ready, it is a bit 
discouraging from translator perspective.
We translators would like to have some automated way to publish 
translated versions of documents
and it allows translators to improve and/or fix translations after the 
initial translation.
Translation publishing is now available.  We just need permissions to 
add the pot file to the project. Moving forward, the process will be 
automated through Zanata in the same way we do the user survey and other 
features.


I propose an idea of using RST file for the edge computing whitepaper 
after the Vancouver summit.
Yes, we're following the standard publishing requirements outlined here: 
https://docs.openstack.org/i18n/latest/en_GB/tools.html
Ildiko said it is being discussed in the edge computing team and the 
foundation but I haven't heard nothing since then.
Or can the foundation publish translations more quickly even though 
the current publishing process is not changed.
If not, I cannot believe this is the right timing to promote 
whitepaper translations.




Thanks,
Akihiro


2018年7月17日(火) 0:27 Jimmy McArthur >:


Sorry, I should have also added... we additionally need
permissions so
that we can add the a new version of the pot file to this project:

https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835

Thanks!
Jimmy



Jimmy McArthur wrote:
> Hi all -
>
> We have both of the current whitepapers up and available for
> translation.  Can we promote these on the Zanata homepage?
>
>

https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684

>
>

https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684

>
>
> Thanks all!
> Jimmy


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-16 Thread Akihiro Motoki
Jimmy,

Does it mean translation **publishing** is ready now?

In the first translation of the edge computing whitepaper, translation
publishing was completely a manual process and it takes too long.
If translation publishing support is not ready, it is a bit discouraging
from translator perspective.
We translators would like to have some automated way to publish translated
versions of documents
and it allows translators to improve and/or fix translations after the
initial translation.

I propose an idea of using RST file for the edge computing whitepaper after
the Vancouver summit.
Ildiko said it is being discussed in the edge computing team and the
foundation but I haven't heard nothing since then.
Or can the foundation publish translations more quickly even though the
current publishing process is not changed.
If not, I cannot believe this is the right timing to promote whitepaper
translations.

Thanks,
Akihiro


2018年7月17日(火) 0:27 Jimmy McArthur :

> Sorry, I should have also added... we additionally need permissions so
> that we can add the a new version of the pot file to this project:
>
> https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835
>
> Thanks!
> Jimmy
>
>
>
> Jimmy McArthur wrote:
> > Hi all -
> >
> > We have both of the current whitepapers up and available for
> > translation.  Can we promote these on the Zanata homepage?
> >
> >
> https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684
> >
> >
> https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684
> >
> >
> > Thanks all!
> > Jimmy
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-16 Thread Jimmy McArthur
Sorry, I should have also added... we additionally need permissions so 
that we can add the a new version of the pot file to this project: 
https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835


Thanks!
Jimmy



Jimmy McArthur wrote:

Hi all -

We have both of the current whitepapers up and available for 
translation.  Can we promote these on the Zanata homepage?


https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684 

https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684 



Thanks all!
Jimmy



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev