From eumel at arcor.de Wed Aug 1 16:08:56 2018 From: eumel at arcor.de (Frank Kloeker) Date: Wed, 01 Aug 2018 18:08:56 +0200 Subject: [OpenStack-I18n] [I18n] Digest 2018/08/01 Message-ID: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> Hello, we are shortly in the beginning of the hot translation phase for Rocky. Few days ahead hard string freeze. We're well prepared. 1. Hard String Freeze In this period and around release we work on stable/rocky branch in each project beside main documentation. Branching is a creeping process, so please use Rocky Dashboard Translation from Zanata mainpage https://translate.openstack.org. Dashboard will be ongoing updated. 2. Whitepaper translation There are two whitepaper in the queue: for Edge Computing and for Containers. The first document is now in a new version available. This was required due the new publishing process. It's easy to convert with Translation Memory the new version from the old one. But there are still issues with publishing so I recommend to focus on project translation starting from next week. 3. PTL election This is also ongoing. See which candidates are running for Stein: https://governance.openstack.org/election/#stein-ptl-candidates 4. Translation Check Site I can announce the official sponsorship for this project by Deutsche Telekom. Hostname and credentials are the same: host: https://i18n.external.otc.telekomcloud.com/ user: i18n pass: Queens2018 There are additional services now in translation string sync: Horizon Dashboard Plugins, Designate, Sahara, Heat, Magnum, Trove. Sync is scheduled hourly. You can review the patch if you want to use your own: https://review.openstack.org/#/c/586867/ 5. Extra-ATC Status My apology because I was too late for collecting the data and propose the Extra ATC. This is mostly approved now: https://review.openstack.org/#/c/586751/ 6. Status Project Doc Translation There is no update. You can translate the openstack-ansible project in Zanata, but at the moment there is now way to push back the strings into project repo. Depends on https://review.openstack.org/#/c/581000/ Any questions or remarks? Please join our next I18n Office Hour, Thursday, 2018/08/02 13:00 UTC in #openstack-i18n (https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting) Please note: There is a spam attack in progress on FreeNode IRC, so channel mode is set +r (registered nick required). kind regards Frank From ianyrchoi at gmail.com Thu Aug 2 02:03:43 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Thu, 2 Aug 2018 11:03:43 +0900 Subject: [OpenStack-I18n] [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation In-Reply-To: <16e69b47c8b71bf6f920ab8f3df61928@arcor.de> References: <5B4CB64F.4060602@openstack.org> <5B4CB93F.6070202@openstack.org> <5B4DF6B4.9030501@openstack.org> <7f053a98-718b-0470-9ffa-934f0e715a76@gmail.com> <5B4E132E.5050607@openstack.org> <5B50A476.8010606@openstack.org> <5B5F295F.3090608@openstack.org> <1f5afd62cc3a9a8923586a404e707366@arcor.de> <16e69b47c8b71bf6f920ab8f3df61928@arcor.de> Message-ID: <83a0d94f-dc74-e1c1-951b-1fcec2fca6f1@gmail.com> 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&T. 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 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 [7] >>> >>> 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 >> >>> [8] 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 >> >>> [9] >>> >> https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684 >> >>> [10] Thanks all! >>> Jimmy >>> >>> >> __________________________________________________________________________ >> >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe [11] >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> [12] >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe [11] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [12] >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe [11] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [12] >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe [11] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [12] >> >> >> >> Links: >> ------ >> [1] >> https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center >> >> [2] >> https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack >> >> [3] >> https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing >> >> [4] >> https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192 >> >> [5] https://docs.openstack.org/i18n/latest/tools.html >> [6] >> https://github.com/OpenStackweb/openstack-org/blob/master/installation.md >> [7] https://docs.openstack.org/i18n/latest/en_GB/tools.html >> [8] >> https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835 >> >> [9] >> https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684 >> >> [10] >> https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684 >> >> [11] >> http://OpenStack-dev-request at lists.openstack.org?subject:unsubscribe >> [12] 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 From eumel at arcor.de Fri Aug 3 20:30:51 2018 From: eumel at arcor.de (Frank Kloeker) Date: Fri, 03 Aug 2018 22:30:51 +0200 Subject: [OpenStack-I18n] [I18n] Digest 2018/08/01 In-Reply-To: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> References: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> Message-ID: Am 2018-08-01 18:08, schrieb Frank Kloeker: [...] > 2. Whitepaper translation > There are two whitepaper in the queue: for Edge Computing and for > Containers. The first document is now in a new version available. This > was required due the new publishing process. It's easy to convert with > Translation Memory the new version from the old one. But there are > still issues with publishing so I recommend to focus on project > translation starting from next week. There is a fast update on this topic: https://www.openstack.org/containers/ https://www.openstack.org/edge-computing/ The translated versions are now online! Please help to translate the Chinese version of Edge Computing whitepaper again in the new format and scale up also in other languages. thx Frank From eumel at arcor.de Fri Aug 3 20:41:08 2018 From: eumel at arcor.de (Frank Kloeker) Date: Fri, 03 Aug 2018 22:41:08 +0200 Subject: [OpenStack-I18n] I18n ATC status Message-ID: <94f8888a1ee8478ee07bb1c9af0c8a1e@arcor.de> Hello, during the approval process for Extra-ATC in I18n we experienced one issue again: Foundation membership. Your ATC status for contribution is out of question, but for elections of PTL/UC/TC/anything is Foundation membership absolutely required. If you are using for Foundation membership and Zanata the same e-mail address, then you're fine. But if these addresses are different, it's required to configure the e-mail address for Zanata registration as second e-mail address in your Foundation membership profile. You can check your collected status on https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics#Rocky_cycle_.282018-01-11_to_2018-07-09.29 many thanks Frank From aj at suse.com Sat Aug 4 14:39:54 2018 From: aj at suse.com (Andreas Jaeger) Date: Sat, 4 Aug 2018 16:39:54 +0200 Subject: [OpenStack-I18n] [I18n] Digest 2018/08/01 In-Reply-To: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> References: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> Message-ID: <5a310dca-f204-d6aa-0718-f7a782ce94ad@suse.com> On 2018-08-01 18:08, Frank Kloeker wrote: > Hello, > > we are shortly in the beginning of the hot translation phase for Rocky. > Few days ahead hard string freeze. We're well prepared. > > 1. Hard String Freeze > In this period and around release we work on stable/rocky branch in each > project beside main documentation. Branching is a creeping process, so > please use Rocky Dashboard Translation from Zanata mainpage > https://translate.openstack.org. Dashboard will be ongoing updated. Frank, I do not see any stable-rocky branches setup in translate.openstack.org. The stable/rocky branches have been created everywhere, so you need to create them on translate.openstack.org as well, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From eumel at arcor.de Mon Aug 6 19:03:45 2018 From: eumel at arcor.de (Frank Kloeker) Date: Mon, 06 Aug 2018 21:03:45 +0200 Subject: [OpenStack-I18n] I18n ATC status In-Reply-To: <94f8888a1ee8478ee07bb1c9af0c8a1e@arcor.de> References: <94f8888a1ee8478ee07bb1c9af0c8a1e@arcor.de> Message-ID: <11854b792d5d82c0c7a63901702d4a24@arcor.de> Am 2018-08-03 22:41, schrieb Frank Kloeker: > Hello, > > during the approval process for Extra-ATC in I18n we experienced one > issue again: Foundation membership. > Your ATC status for contribution is out of question, but for elections > of PTL/UC/TC/anything is Foundation membership absolutely required. If > you are using for Foundation membership and Zanata the same e-mail > address, then you're fine. But if these addresses are different, it's > required to configure the e-mail address for Zanata registration as > second e-mail address in your Foundation membership profile. You can > check your collected status on > https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics#Rocky_cycle_.282018-01-11_to_2018-07-09.29 Update: All proposed Extra-ATC for I18n are meanwhile approved. Check out the list: https://governance.openstack.org/tc/reference/projects/i18n.html Thanks for contributing to OpenStack and see you in Berlin :-) Frank From eumel at arcor.de Fri Aug 10 10:28:58 2018 From: eumel at arcor.de (Frank Kloeker) Date: Fri, 10 Aug 2018 12:28:58 +0200 Subject: [OpenStack-I18n] [I18n] Digest 2018/08/10 In-Reply-To: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> References: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> Message-ID: Hello, some updates from my side what happened this week: 1. PTL election is done and I'm the I18n PTL for Stein. Thanks for your trust and I'm looking forward to draw the project goals for Stein in the next weeks. 2. ATC codes are shipped. Early bird tickets for Berlin Summit are available till August 22nd. 3. Project update/Project onboarding session Berlin Summit. Needs to be define. If you are interested as a volunteer for project onboarding or project update session, let me know. 4. Zuul-Translation Jobs. Maybe you've seen it on IRC or dev-ML, we had an issue with the translation sync jobs in Zuul. This is fixed now and we're back in normal operation. For the future we want to simplify the process, a proposal for new job templates are already on the way: https://review.openstack.org/#/c/589372/ 5. Whitepaper translation. As I already wrote, the publishing issues are fixed and also the translator credits are on the website. Now there is only an issue to collect metrics in Stackalytics for this 2 projects. 6. Release weeks. Most of the projects branched now to stable/rocky. Please use the Rocky Translation Dashboard on Zanata. There are the right branched for different project linked and I refresh the board daily. 7. Translation Check Site. Is updated to stable/rocky and syncs the translation strings also from the same branch if available (i.e. Horizon). That's all. You've still a happy summer :-) kind regards Frank From yukokatabami at gmail.com Mon Aug 13 00:13:30 2018 From: yukokatabami at gmail.com (Yuko Katabami) Date: Mon, 13 Aug 2018 10:13:30 +1000 Subject: [OpenStack-I18n] [I18n] Digest 2018/08/10 In-Reply-To: References: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> Message-ID: Hi Frank, On 10 August 2018 at 20:28, Frank Kloeker wrote: > Hello, > > some updates from my side what happened this week: > > 1. PTL election is done and I'm the I18n PTL for Stein. Thanks for your > trust and I'm looking forward to draw the project goals for Stein in the > next weeks. > > 2. ATC codes are shipped. Early bird tickets for Berlin Summit are > available till August 22nd. > > 3. Project update/Project onboarding session Berlin Summit. Needs to be > define. If you are interested as a volunteer for project onboarding or > project update session, let me know. > > 4. Zuul-Translation Jobs. Maybe you've seen it on IRC or dev-ML, we had an > issue with the translation sync jobs in Zuul. This is fixed now and we're > back in normal operation. For the future we want to simplify the process, a > proposal for new job templates are already on the way: > https://review.openstack.org/#/c/589372/ > > 5. Whitepaper translation. As I already wrote, the publishing issues are > fixed and also the translator credits are on the website. Now there is only > an issue to collect metrics in Stackalytics for this 2 projects. > > 6. Release weeks. Most of the projects branched now to stable/rocky. > Please use the Rocky Translation Dashboard on Zanata. There are the right > branched for different project linked and I refresh the board daily. > Thank you very much for your updates. Just a quick question. The changes we apply to the stable-rocky version in Zanata will be merged to master later? If so, what timing will it be? Kind regards, Yuko > > 7. Translation Check Site. Is updated to stable/rocky and syncs the > translation strings also from the same branch if available (i.e. Horizon). > > That's all. You've still a happy summer :-) > > kind regards > > Frank > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > -------------- next part -------------- An HTML attachment was scrubbed... URL: From eumel at arcor.de Mon Aug 13 09:45:54 2018 From: eumel at arcor.de (Frank Kloeker) Date: Mon, 13 Aug 2018 11:45:54 +0200 Subject: [OpenStack-I18n] [I18n] Digest 2018/08/10 In-Reply-To: References: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> Message-ID: Am 2018-08-13 02:13, schrieb Yuko Katabami: > Hi Frank, > > On 10 August 2018 at 20:28, Frank Kloeker wrote: [...] >> 6. Release weeks. Most of the projects branched now to stable/rocky. >> Please use the Rocky Translation Dashboard on Zanata. There are the >> right branched for different project linked and I refresh the board >> daily. > > Thank you very much for your updates. > Just a quick question. > The changes we apply to the stable-rocky version in Zanata will be > merged to master later? > If so, what timing will it be? Hi Yuko, yes! As usually we bring back stable branch back to master between 1-2 weeks after release. Translation will be merged in Zanata and we'll work then on master. kind regards Frank From yukokatabami at gmail.com Mon Aug 13 12:57:46 2018 From: yukokatabami at gmail.com (Yuko Katabami) Date: Mon, 13 Aug 2018 22:57:46 +1000 Subject: [OpenStack-I18n] [I18n] Digest 2018/08/10 In-Reply-To: References: <02bd6bfa0d80242b4b1f200b81a80bb2@arcor.de> Message-ID: On 13 August 2018 at 19:45, Frank Kloeker wrote: > Am 2018-08-13 02:13, schrieb Yuko Katabami: > >> Hi Frank, >> >> On 10 August 2018 at 20:28, Frank Kloeker wrote: >> > [...] > >> 6. Release weeks. Most of the projects branched now to stable/rocky. >>> Please use the Rocky Translation Dashboard on Zanata. There are the >>> right branched for different project linked and I refresh the board >>> daily. >>> >> >> Thank you very much for your updates. >> Just a quick question. >> The changes we apply to the stable-rocky version in Zanata will be >> merged to master later? >> If so, what timing will it be? >> > > Hi Yuko, > > yes! As usually we bring back stable branch back to master between 1-2 > weeks after release. Translation will be merged in Zanata and we'll work > then on master. > Hi Frank, Thank you very much for your reply! I will keep working on stable-rocky then. Kind regards, Yuko > > kind regards > > Frank > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cloudsuhartono at gmail.com Tue Aug 21 01:49:15 2018 From: cloudsuhartono at gmail.com (Cloud Suhartono) Date: Tue, 21 Aug 2018 08:49:15 +0700 Subject: [OpenStack-I18n] Indonesian translations on the edge whitepaper New! Message-ID: I do not see any Indonesian translation on the pot-translation [1] although I have done 100% for it on the master [2]. Can anyone help me ! Thank you - Suhartono - [1] https://translate.openstack.org/iteration/view/edge-computing/pot-translation/languages/id?dswid=9893 [2] https://translate.openstack.org/iteration/view/edge-computing/master/languages/id?dswid=-275 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ianyrchoi at gmail.com Wed Aug 22 16:42:49 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Thu, 23 Aug 2018 01:42:49 +0900 Subject: [OpenStack-I18n] Indonesian translations on the edge whitepaper New! In-Reply-To: References: Message-ID: <4bad2017-3f50-a99e-fcaf-4885fb7e6410@gmail.com> Hello Suhartono, There have been lots of discussion on the format of edge computing whitepaper translation. [2] was for PDF format on edge computing whitepaper translation, but we concluded that lots of tedious manual work on creating so many PDF files with multiple languages were required and the format is now changed to HTML based format [1]. (Reference: [3]) So would you kindly re-translate on [1] by referring the translated strings on [2] which are shown on the bottom part in Zanata? Then I am sure that Indonesian language tab will be automatically shown in [4] with in one day after translation has 100% (ideally, unless there is no sync problem on translation resources and translated strings have no error). With many thanks, /Ian [3] http://lists.openstack.org/pipermail/openstack-i18n/2018-August/003292.html [4] https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center Cloud Suhartono wrote on 8/21/2018 10:49 AM: > I do not see any Indonesian translation on the pot-translation [1] > although I have done 100% for it on the master [2]. > > Can anyone help me ! > > Thank you > - Suhartono - > > [1] > https://translate.openstack.org/iteration/view/edge-computing/pot-translation/languages/id?dswid=9893 > > [2] > https://translate.openstack.org/iteration/view/edge-computing/master/languages/id?dswid=-275 > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n -------------- next part -------------- An HTML attachment was scrubbed... URL: From cloudsuhartono at gmail.com Wed Aug 22 17:27:11 2018 From: cloudsuhartono at gmail.com (Cloud Suhartono) Date: Thu, 23 Aug 2018 00:27:11 +0700 Subject: [OpenStack-I18n] Indonesian translations on the edge whitepaper New! In-Reply-To: <4bad2017-3f50-a99e-fcaf-4885fb7e6410@gmail.com> References: <4bad2017-3f50-a99e-fcaf-4885fb7e6410@gmail.com> Message-ID: Thank you for the clarification. I am trying to re-translate mine. /Suhartono On Wed, Aug 22, 2018, 23:42 Ian Y. Choi wrote: > Hello Suhartono, > > There have been lots of discussion on the format of edge computing > whitepaper translation. > [2] was for PDF format on edge computing whitepaper translation, but we > concluded that lots of tedious > manual work on creating so many PDF files with multiple languages were > required and the format is now changed to HTML based format [1]. > (Reference: [3]) > > So would you kindly re-translate on [1] by referring the translated > strings on [2] which are shown on the bottom part in Zanata? > Then I am sure that Indonesian language tab will be automatically shown in > [4] with in one day after translation has 100% > (ideally, unless there is no sync problem on translation resources and > translated strings have no error). > > > With many thanks, > > /Ian > > [3] > http://lists.openstack.org/pipermail/openstack-i18n/2018-August/003292.html > [4] > https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center > > Cloud Suhartono wrote on 8/21/2018 10:49 AM: > > I do not see any Indonesian translation on the pot-translation [1] > although I have done 100% for it on the master [2]. > > Can anyone help me ! > > Thank you > - Suhartono - > > [1] > https://translate.openstack.org/iteration/view/edge-computing/pot-translation/languages/id?dswid=9893 > > [2] > https://translate.openstack.org/iteration/view/edge-computing/master/languages/id?dswid=-275 > > > _______________________________________________ > OpenStack-I18n mailing listOpenStack-I18n at lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: