- OpenStack-I18n - lists.openstack.org

[I18n] Digest 2018/08/01
by Frank Kloeker 13 Aug '18

13 Aug '18

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

3 6

I18n ATC status
by Frank Kloeker 06 Aug '18

06 Aug '18

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… many thanks Frank

1 1

Re: [OpenStack-I18n] [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation
by Ian Y. Choi 01 Aug '18

01 Aug '18

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.… [2] http://git.openstack.org/cgit/openstack/i18n/tree/doc/source/locale/de/LC_M… 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 <eumel(a)arcor.de> wrote: >> >>> Hi Jimmy, >>> >>> from the GUI I'll get this link: >>> >> https://translate.openstack.org/rest/file/translation/edge-computing/pot-tr… >> >>> [1] >>> >>> paper version are only in container whitepaper: >>> >>> >> https://translate.openstack.org/rest/file/translation/leveraging-containers… >> >>> [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?d… >> >>> [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-translati… >> >>> [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=… >> >>> [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-openstac… >> >>> [9] >>> >> https://translate.openstack.org/iteration/view/edge-computing/master/docume… >> >>> [10] Thanks all! >>> Jimmy >>> >>> >> __________________________________________________________________________ >> >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> OpenStack-dev-request@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@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@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@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-tr… >> >> [2] >> https://translate.openstack.org/rest/file/translation/leveraging-containers… >> >> [3] >> https://translate.openstack.org/rest/file/translation/papers/papers/de/po?d… >> >> [4] >> https://translate.openstack.org/iteration/view/edge-computing/pot-translati… >> >> [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=… >> >> [9] >> https://translate.openstack.org/project/view/leveraging-containers-openstac… >> >> [10] >> https://translate.openstack.org/iteration/view/edge-computing/master/docume… >> >> [11] >> http://OpenStack-dev-request@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@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[I18n] [PTL] [Election] Candidacy for I18n PTL in Stein Cycle
by Frank Kloeker 25 Jul '18

25 Jul '18

[posted & mailed] https://review.openstack.org/#/c/585663/ This is my announcement for re-candidacy as I18n PTL in Stein Cycle. At first a quick review what we've done in the last cycle: 1. Zanata upgrade done. As one of the first community's we're running Zanata Release 4 in production. A big success and a great user experiense for all. 2. Translation Check Site done. We were able to win Deutsche Telekom as sponsor for resources, so now we are able to host our own Translation Check Site. From my point of view this solves different problems which we had in the past and now we can check translation strings very fast on our requirements. 3. Aquire more people to the team. I had great experiences during the OpenStack Days in Krakow and Budapest. I shared informationen what our team is doing and how I18n works in the OpenStack Community. I've got many inspirations and hopefully some new team members :-) What I mostly like is getting things done. In this cycle we should get ready project doc translations. We started already with some projects as a proof of concept and we're still working on it. To get that around, involve more projects and involve more project team members for translations is the biggest challenge for me in this cycle. On the other hand we have Edge Computing whitepaper and Container whitepaper on our translation plan. With a new technology in use to publish the translation results very fast on the web page. Beside that we have the OpenStack Summit Berlin in that cycle. For me a special event, since I live and work in Berlin. I expect a lot of collaboration and knowledge sharing with I18n and the OpenStack Community in general. That's my plan for Stein, I'm looking forward to your vote. Frank Email: eumel(a)arcor.de IRC: eumel8 Twitter: eumel_8 OpenStack Profile: https://www.openstack.org/community/members/profile/45058/frank-kloeker

1 0

Re: [OpenStack-I18n] Zanata user email from "alexanderloew2": Inquiry on Zanata
by Ian Y. Choi 15 Jul '18

15 Jul '18

Hello Alexander, I am checking your message now - a little bit late since your Zanata message is sent to me and Frank, and such request was classified as a spam in my mail box. https://docs.openstack.org/i18n/latest/glossary.html describes how to add translated words to the glossary and you can see i18n repository through http://git.openstack.org/cgit/openstack/i18n and https://github.com/openstack/i18n (mirrored site). With many thanks, /Ian Zanata wrote on 7/14/2018 5:13 AM: > > Dear Administrator, > > Zanata user "Alexander Loew" with id "alexanderloew2" has sent the > following message: > > ------------------------------------------------------------------------ > how can I add translation to the glossary? > ------------------------------------------------------------------------ > > You can reply to Alexander Loew at alexander.loew(a)innovo-cloud.de > > ------------------------------------------------------------------------ > > You are receiving this mail because: > You are an administrator > > This message generated by Zanata running at: > https://translate.openstack.org <https://translate.openstack.org> >

1 0

[docs][i18n][ptg] PTG infos on Etherpad
by Frank Kloeker 13 Jul '18

13 Jul '18

Hello, the Docs and I18n team will also present during the PTG in Denver. The rough plan told us on Monday/Tuesday. As usually we're in the same room and will use also the same Etherpad on [1], which I have shameless copied from the last PTG in Denver, so we have all this usefull links for Station 26 already there :) Please write down your topics and your possible participation. The Etherpad from the previous PTG is also linked as a reminder. many thanks Frank [1] https://etherpad.openstack.org/p/docs-i18n-ptg-stein

1 0

[I18n] IRC Office hours: 2018/07/05 13:00-14:00 UTC
by Frank Kloeker 11 Jul '18

11 Jul '18

Hello, good to be back. Still sorting emails, messages and things. Let's meet on Thursday in our team meeting in the new Office Hour format: 2018/07/05 13:00-14:00 UTC If you have anything to share please let us know on wiki page [1] kind regards Frank [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

2 2

Re: [OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing Whitepaper Translation
by Jimmy McArthur 25 Jun '18

25 Jun '18

We are currently targeting June 25 for the initial version of the Edge whitepaper. However, I'll know more by EOW next. Cheers, Jimmy Ildiko Vancsa wrote: > Hi Akihiro, > > It is on our priority list to put up the translated versions in an online format as well as work out to have the .po files available. > > Jimmy is looking into it and will give an update once we got some progress. > > Thanks and Best Regards, > Ildikó > > >> On 2018. Jun 8., at 10:14, Akihiro Motoki<amotoki(a)gmail.com> wrote: >> >> Hi all, >> >> # I added edge-computing ML as the edge computing team uses a separate list other than the SIG ML. >> # The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML. >> >> What is the next step of the translation of the edge computing white paper with RST? >> My temporary translation publishing [1] should not be published as-is due to the CC BY-ND license. This is to prove how it works. >> I would like to move this forward and am happy to help the setup of a repo if needed. >> >> Where can we discuss this? >> The edge computing group meeting is not listed at http://eavesdrop.openstack.org/ and I don't know when and where it happens. >> >> [1] https://amotoki.github.io/edge-computing-whitepaper/ >> >> Thanks, >> Akihiro >> >> 2018年5月29日(火) 23:37 Akihiro Motoki<amotoki(a)gmail.com>: >> Hi Ildiko and all, >> >> I am happy to hear that HTML-based publishing is now on the table :) >> I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver. >> RST based process is used much in the community and translation publishinng of project docs which Ian and us are working on will make the continuous publishing easier. >> I am happy to help setting up a new doc infrastructure and/or publishing translations. >> >> Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one. >> Hopefully we can get a good conclusion for further similar cases. >> >> Thanks, >> Akihiro >> >> >> >> 2018年5月29日(火) 23:19 Ildiko Vancsa<ildiko.vancsa(a)gmail.com>: >> Hi Akihiro and All, >> >> Thank you for your efforts on helping with publishing the white paper in additional languages. >> >> I talked to Ian and Frank last week about this topic and the conundrum on the Foundation side whether or not to do the print version for the translations as that is what slows down the process a lot due to the design work it requires. >> >> We got to the conclusion with our team from the Foundation (cc’ed Allison, Jimmy and Wes) to do HTML-based publishing to reduce this overhead. We need to clarify now on the process and as Jeremy indicated the licensing as well. >> >> Thanks, >> Ildikó >> >> >>> On 2018. May 29., at 15:50, Jeremy Stanley<fungi(a)yuggoth.org> wrote: >>> >>> On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: >>> [...] >>>> NOTE: Anyway I need to grant it from the foundation because CC >>>> Attribution-NoDerivatives 4.0 International license does not allow >>>> me to share translations without permission. I updated this files >>>> only for discussion and will close this soon. >>> [...] >>> >>> It seems like this is a really poor choice of license as it's >>> impairing open collaboration. Even Creative Commons suggests that >>> the CC BY-ND license is unsuitable for free cultural works: >>> >>> https://creativecommons.org/share-your-work/public-domain/freeworks/ >>> >>> We should see about getting this changed to CC BY like is used for >>> other collaborative works produced by our community. >>> -- >>> Jeremy Stanley >>> _______________________________________________ >>> openstack-sigs mailing list >>> openstack-sigs(a)lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> _______________________________________________ >> openstack-sigs mailing list >> openstack-sigs(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> _______________________________________________ >> Edge-computing mailing list >> Edge-computing(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing >

1 1

[Bug 1778474] [NEW] 安装和配置 in Installation Guide
by Jack Wong 25 Jun '18

25 Jun '18

Public bug reported: 注解教程使用带有``mod_wsgi``的Apache HTTP服务器来服务认证服务请求，端口为5000和35357。缺省情况下，Kestone服务仍然监听这些端口。然而，本教程手动禁用keystone服务。拼写错误缺省情况下，Keystone服务仍然监听 ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1778474 Title: 安装和配置 in Installation Guide Status in openstack i18n: New Bug description: 注解教程使用带有``mod_wsgi``的Apache HTTP服务器来服务认证服务请求，端口为5000和35357。缺省情况下，Kestone服务仍然监听这些端口。然而，本教程手动禁用keystone服务。拼写错误缺省情况下，Keystone服务仍然监听 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1778474/+subscriptions

1 0

Re: [OpenStack-I18n] [Openstack-sigs] Edge Computing Whitepaper Translation
by Akihiro Motoki 08 Jun '18

08 Jun '18

Hi Ildiko and all, I am happy to hear that HTML-based publishing is now on the table :) I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver. RST based process is used much in the community and translation publishinng of project docs which Ian and us are working on will make the continuous publishing easier. I am happy to help setting up a new doc infrastructure and/or publishing translations. Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one. Hopefully we can get a good conclusion for further similar cases. Thanks, Akihiro 2018年5月29日(火) 23:19 Ildiko Vancsa <ildiko.vancsa(a)gmail.com>: > Hi Akihiro and All, > > Thank you for your efforts on helping with publishing the white paper in > additional languages. > > I talked to Ian and Frank last week about this topic and the conundrum on > the Foundation side whether or not to do the print version for the > translations as that is what slows down the process a lot due to the design > work it requires. > > We got to the conclusion with our team from the Foundation (cc’ed Allison, > Jimmy and Wes) to do HTML-based publishing to reduce this overhead. We need > to clarify now on the process and as Jeremy indicated the licensing as well. > > Thanks, > Ildikó > > > > On 2018. May 29., at 15:50, Jeremy Stanley <fungi(a)yuggoth.org> wrote: > > > > On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: > > [...] > >> NOTE: Anyway I need to grant it from the foundation because CC > >> Attribution-NoDerivatives 4.0 International license does not allow > >> me to share translations without permission. I updated this files > >> only for discussion and will close this soon. > > [...] > > > > It seems like this is a really poor choice of license as it's > > impairing open collaboration. Even Creative Commons suggests that > > the CC BY-ND license is unsuitable for free cultural works: > > > > https://creativecommons.org/share-your-work/public-domain/freeworks/ > > > > We should see about getting this changed to CC BY like is used for > > other collaborative works produced by our community. > > -- > > Jeremy Stanley > > _______________________________________________ > > openstack-sigs mailing list > > openstack-sigs(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > > > _______________________________________________ > openstack-sigs mailing list > openstack-sigs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >

4 6