Open Stack

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 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-request at 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-request at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>