Thursday, 2018-07-19

*** jamesmcarthur has quit IRC00:08
*** jamesmcarthur has joined #openstack-i18n00:11
*** jamesmcarthur has quit IRC00:13
*** jamesmcarthur has joined #openstack-i18n00:14
*** jamesmcarthur has quit IRC00:18
*** jamesmcarthur has joined #openstack-i18n00:18
*** itlinux_ has joined #openstack-i18n00:21
*** itlinux has quit IRC00:23
*** jamesmcarthur has quit IRC00:47
*** itlinux_ has quit IRC00:49
*** itlinux has joined #openstack-i18n01:17
*** itlinux has quit IRC02:19
*** jamesmcarthur has joined #openstack-i18n02:33
*** jamesmcarthur has quit IRC02:38
*** aeng has joined #openstack-i18n02:56
*** pcaruana has joined #openstack-i18n04:23
*** pcaruana has quit IRC04:34
*** v12aml has quit IRC05:29
*** johnsom has quit IRC05:29
*** DuncanT_ has joined #openstack-i18n05:30
*** johnsom has joined #openstack-i18n05:30
*** DuncanT has quit IRC05:31
*** v12aml has joined #openstack-i18n05:34
*** aeng has quit IRC06:21
*** pcaruana has joined #openstack-i18n06:37
*** rcernin has quit IRC07:29
*** tosky has joined #openstack-i18n07:37
*** rsimai_away is now known as rsimai07:40
*** eumel8 has joined #openstack-i18n08:10
ianychoieumel8, oh hi - I couldn't see your online status for recent a few days :)08:14
eumel8ianychoi: good morning08:23
eumel8yes, lots to do08:23
ianychoieumel8, good morning (Berlin)!08:23
ianychoiSeems very busy :)08:24
eumel8try to organize something for Berlin Summit08:24
eumel8and follow email conversation08:25
eumel8ianychoi: I think we have a chat today regarding whitepaper translation08:26
eumel8container and edge08:27
ianychoieumel8, yep.. discussing in office hour (13 UTC) would be fine? Or we can discuss more08:27
eumel813 UTC is fine for me08:28
eumel8ianychoi: maybe some suggestions for https://review.openstack.org/#/c/581000/08:30
ianychoieumel8, I see I have not seen the change on the review - I will see before 13 UTC :)08:31
eumel8thx08:32
ianychoiYou're welcome :)08:33
*** tesseract has joined #openstack-i18n08:41
*** jamesmcarthur has joined #openstack-i18n10:34
*** jamesmcarthur has quit IRC10:39
*** rsimai is now known as rsimai_away12:33
eumel85 min to the I18n Office Hour12:55
-openstackstatus- NOTICE: logs.openstack.org is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown.12:56
*** ChanServ changes topic to "logs.openstack.org is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown."12:56
eumel8#startmeeting openstack_i18n_office_hour13:00
openstackMeeting started Thu Jul 19 13:00:01 2018 UTC and is due to finish in 60 minutes.  The chair is eumel8. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: openstack_i18n_office_hour)"13:00
openstackThe meeting name has been set to 'openstack_i18n_office_hour'13:00
ianychoiHi13:00
*** jamesmcarthur_ has joined #openstack-i18n13:02
*** jamesmcarthur has joined #openstack-i18n13:03
jamesmcarthurianychoi: do you have a few minutes to chat re: Edge translation?13:04
eumel8Hello13:04
eumel8Hi ianychoi, jamesmcarthur13:05
jamesmcarthurhello!13:05
ianychoijamesmcarthur, hello!13:05
*** aprice has joined #openstack-i18n13:06
eumel8jamesmcarthur: I've got you. You want a new version for Edge Computing guide now in HTML style. This is valid for me.13:06
jamesmcarthurYeah, I just wanted to hopefully clear up any concerns about the way we went about it.13:06
ianychoiIs it available now (Edge Computing white paper for HTML)?13:06
jamesmcarthurAnd discuss possible changes that could make it easier for hte translation team13:07
eumel8jamesmcarthur: yes, it's clear now. Also about the costs for pdf design13:07
ianychoiI have been waiting for seeing on Zanata since I wanted to see differences on source strings.13:07
jamesmcarthurianychoi: I don't think Sebastian has uploaded it yet, but will put up this morning.13:07
ianychoijamesmcarthur, aha.. thanks :)13:07
jamesmcarthureumel8: ok great... it's unfortunate, b/c the PDF is obviously a nicer output13:07
jamesmcarthurbut it's just very cost prohibitive for the foundation13:08
jamesmcarthurI also want to discuss the RST format that Akihiro created.  Is that the preferred method for i18n team?13:09
ianychoijamesmcarthur, I understand - I was initially worried about how translated PDF stuff were generated since the work needs some human-effort13:09
jamesmcarthurianychoi: I'll update that email thread as soon as it's up. Thanks to you and eumel8 for adjust the Zanata permissions for us.13:09
amotokihoenstly I have no preference on the format13:10
jamesmcarthuroh hi amotoki: :)13:11
ianychoiJust one thing I want to clear now is that translation start on txt files assumed that translated publish from translated resources would be available to all the languages?13:11
amotokiany format would be okay if it can be automated and continuous publishing is achieved13:11
jamesmcarthurright, so the new version that we put together will work the same way as user survey13:11
jamesmcarthurwhere we do either a manual pull from zanata OR it will update via a nightly pull13:12
amotokiwe already have a way to publish documents continuously for RST format. there is no more reason than that.13:12
jamesmcarthurOnce a language po file is marked as complete, we will ingest it and update our db w/ the po files. Then the language will automatically appear as a selection in the dropdown.13:12
amotokiyeah, I know how user survey translation version is published.13:12
amotokijamesmcarthur: is there any easy way to update translations?13:13
jamesmcarthuramotoki: can you clarify the question? Do you mean, is there a way to modify the translation after it's published?13:13
amotokifrom my experience the initial version of translation is NOT perfect and we usually updates trnaslation after reading the initial publishment13:13
jamesmcarthuri see13:14
amotokijamesmcarthur: yes!13:14
jamesmcarthuryes. if you update the po files, we will reingest nightly13:14
ianychoiI18n team is accustomed with RST-based publication, and I am sure that Foundation is more accustomed with dealing with Silverstripe. Being open on how publish using Silverstripe is worked and when Silverstripe-based translated strings are updated would be nice13:14
amotokithis is what we expect for most openstack translations13:14
jamesmcarthurThe problem is, it's not immediate. We just do the updates nightly. I can see if we can increase the update intervals.13:14
amotokiit sounds enough.13:15
ianychoijamesmcarthur, could you share when it is updated? For example, translated strings RST documents are synced from 6:00 UTC and the job usually finishes within 3-4 hours.13:15
jamesmcarthurIdeally, I'd like to get to a place where it's painless for i18n team. We want to start doing more translations.13:15
amotokitranslations for RST documents from the project teams are updated by a daily job13:15
jamesmcarthuramotoki: we do the same. It's a nightly job. Runs around 1am Central, I believe13:16
jamesmcarthurAnd it's very quick.13:16
ianychoijamesmcarthur, thank u for good info13:16
amotokifor the edge compuiting whitepaper, translations other than zh-CN are published now?13:16
jamesmcarthurThat's why I think we could run it more frequently on shorter intervals.  I'll check on that13:17
amotokire the frequency of the update, I believe daily is enough13:17
jamesmcarthuramotoki: not yet. We need the RST version moved over to the po files, and then we will turn on the new HTML veresion of the Edge page13:17
amotokido we convert it into RST version?13:18
jamesmcarthuramotoki: if you could, that would be ideal.  However, there will be some slight differences b/c the Edge paper is HTML i/o PDF.13:19
jamesmcarthurSebastian's putting the file up now in the original Edge project13:19
ianychoiI think we might need to discuss: 1) when can we regard *release*d publication on whitepapers 2) what if the source of *release*d whitepapers is updated in future? 3) Can Foundation also provide translation checksite for whitepapers before final releasing, as what we did for user survey translation? 4) In a long term, I would like to document similar as https://docs.openstack.org/i18n/latest/release_management.html13:19
amotokiianychoi: nice summary!! thanks13:20
jamesmcarthur1) Moving forward, translations on whitepapers will publish nightly. This is a brand new Silverstripe template, so we want to make sure it's not broken before we publish.13:20
jamesmcarthur2) If the source of the whitepaper (the HTML), it updated in the future, we will resubmit updated pot files to Zanata13:21
jamesmcarthur(like we do w/ user survey)13:21
jamesmcarthur3) I think we can set up another translation review site... let me check on a few things.13:22
jamesmcarthur4) I'd be happy to work with you on documenting the process :)13:22
amotokifor 3), we can check translations with published versions, though it would be nice if we can check translations before publishing it but it is not a requirement :)13:23
jamesmcarthuramotoki: I completely agree. I've been noodling on a few things this morning. I'm going to talk with smarcet and bounce some ideas off of him.13:23
jamesmcarthurI'd prefer something close to real time review of po files13:24
jamesmcarthurin the proper HTML format13:24
ianychoiBy the way, for PDF stuff, translating idml file (one of InDesign source files for text) is available on Zanata and I have been testing a little bit through translate-dev site: https://translate-dev.openstack.org/iteration/view/ianychoi-test-odp/master/documents?docId=OpenStack_EdgeWhitepaper_v3_online.idml (screenshot: https://prnt.sc/k8fpg1 and https://prnt.sc/k8fpqd ). After downloading translated idml file & replacing to a source should13:24
ianychoiwork by additionally setting fonts unless translated strings is not longer than original strings..13:24
jamesmcarthurThat seems easier to do for whitepapers than for user survey13:24
jamesmcarthurianychoi "unless translated strings is not longer than original strings" - that's really the crux of the problem13:25
ianychoi(I do not have InDesign license but last week I tested with my designer colleague)13:25
ianychoijamesmcarthur, yes.. I really understand this problem after my trial. If a designer manually copies & pastes translated strings, the problem would be much worse..13:26
jamesmcarthurI'll take a look at the idml test13:26
jamesmcarthurianychoi: right... it can get messy very quickly13:26
jamesmcarthurand something that seems "right" to the eye, might make no sense in the actual language13:27
jamesmcarthurSo unless you're fluent in all languages, it makes it tough to sort out the layout.13:27
ianychoiI agree and for PDF stuff, moving to HTML for translation targets is preferred way for me.13:27
jamesmcarthurok cool13:28
amotoki+10013:28
amotokifor 4) the process of the publishing translations, perhaps the i18n team would like to clarify how it is published because the delay of the edge computing translation publishing make the i18n team nervous.13:28
amotokithe point is how we can automate the process13:28
amotokiit seems we are in the same page :)13:28
jamesmcarthuramotoki: right, agree 100%13:28
jamesmcarthurmoving forward, the only delay will be the nightly update. I mean, once the po files are complete, we should ingest and display automatically on the site.13:29
jamesmcarthurthe new silverstripe whitepaper template we developed for Edge and Containers will work for all future whitepapers13:29
jamesmcarthurand will create the pot files automatically13:29
jamesmcarthurI hope that we will see a much quicker turn around13:30
ianychoiThat's fine since po <-> rst sync is also daily - but it would be nice if a translator with development knowledge can test locally or eumel8 previously shared translation checksite and he updated frequently for horizon... :)13:30
jamesmcarthurFurther, I appreciate everyone's patience while we worked on the template.13:30
jamesmcarthurianychoi: right, understood. I'll see if I can come up with a solution for that.13:31
jamesmcarthurI'd say let's just continue to communicate about pain points and see how we can make everyone's life easier.13:31
ianychoijamesmcarthur, thank u :)13:31
amotokiI am happy to see good progress like today's discussion :)13:32
jamesmcarthurOf course! Please feel free to reach out to me on IRC or email if you all are experiencing any problems.13:32
ianychoieumel8 seems to do parallel meeting with other one, but IMO how about announcing translation target on Zanata for whitepapers after clarifying and implementing all the syncs?13:32
jamesmcarthurI'll let everyone know as soon as the edge pot files are up13:32
amotokiperhaps it is better to announce the current situation on how and when translations are published.13:33
amotokiit was explained in the ML thread, but it is better to announce it officially13:34
amotokipersonally I don't think we need to have a notification for every update of POT files.13:34
jamesmcarthuramotoki: sure, just let us know how you'd prefer it to be handled13:35
eumel8I'm here but nothing to add ;) I only can announce my company are graciously support now the I18n translation checksite with resources. Maybe we try to install on the top https://github.com/OpenStackweb/openstack-org/blob/master/installation.md13:35
ianychoiFor edge computing whitepaper, where would be some source string differences on a source string without HTML markup and another source string with HTML markup. Translators can easily translate with translation memory but I am not sure how many similarities on source strings are there (~80%? ~70%?) because of HTML markups.13:35
amotokiyeah, we see some differences in POT/PO files on zanata and the published English vesion of the whitepaper.13:35
ianychoiIf there are so high similarities, then eumel8 might announce that "Please simply check new translation sources for edge computing whitepaper for HTML publish soon within 1-2 weeks"13:36
ianychoiIf similarity ratio is not high, then eumel8 might announce it with longer period for translation..13:37
jamesmcarthurianychoi: I think that's probably the best path. I believe it should be very similar, but I'm not 100% sure where the differences are from the PDF to the HTML13:38
ianychoijamesmcarthur, If you have time during upcoming PTG on Mon or Tue, I would like to discuss how to document such stuff better on I18n contributor guide :)13:38
jamesmcarthurYes sir. That sounds great :)13:39
*** ChanServ changes topic to "(Meeting topic: openstack_i18n_office_hour)"13:39
-openstackstatus- NOTICE: logs.openstack.org is back on-line. Changes with "POST_FAILURE" job results should be rechecked.13:39
jamesmcarthurI'll be sitting in on the Ops meetup most of Mon/Tues, but let's just schedule an hour or so to talk.13:39
ianychoiAha yep about about 1-2 hour would be fine :)13:40
jamesmcarthurOK - I'll send out an invite just so we can hold some time.13:41
ianychoiTranslation memory functionality is so nice in Zanata, although I don't know how to export translation memory in translate.openstack.org13:42
jamesmcarthurI have to run and take my daughter to school. Any other quick thoughts? I can come back online in about 30 minutes.13:43
eumel8all fine, I think13:43
ianychoiTranslation stuff for HTML-based edge computing whitepaper source strings would not be difficult, but I have been thought how we share translation period again for the same document with a little bit different format. If we define process clearly, then that would be fine I think.13:43
ianychoijamesmcarthur, nope please take care of your daughter since family is important :)13:44
jamesmcarthurok :)  Thanks to all of you for your time this morning. I hope I didn't take up all of your office hours!13:44
eumel8that's why we're here ;)13:45
ianychoijamesmcarthur, thanks a lot for coming to I18n office hour!13:45
*** jamesmcarthur has quit IRC13:46
*** jamesmcarthur has joined #openstack-i18n13:46
eumel8so13:47
eumel8other topics?13:47
ianychoieumel8, I wrote a comment on https://review.openstack.org/#/c/581000/ but any other questions on your patch work?13:48
*** jamesmcarthur has quit IRC13:50
eumel8ianychoi: move from L176 to L222? Sorry, I don't get the point13:52
ianychoieumel8, calling "handle_project_doc" function in handle_python_django not in "case "$PROJECT" in" (your patch)13:54
eumel8mhm, but for example i18n isn't a python or django project. So I would keep it separatly.13:55
ianychoieumel8, from my understanding on the shell script, python_django projects can have also releasenotes and documentation13:55
ianychoiThen why releasenote translation support is in python_django? :)13:56
ianychoiAlso, developing per-translation ratio check on doc-install, doc-admin, and so on would be needed...13:56
eumel8yes, but for the future we want to remove this extra rule set for i18n and have only one function for doc translation based on a check if a doc directory is in the repo with a conf file13:58
ianychoiI don't think that my saying only applies to i18n - releasenotes applies to all python_django projects. What I want to tell now is that I want to stay the same as documentation translation support stuff & releasenotes translation support stuff..13:59
ianychoiThe purpose of diving one doc into doc-admin, doc-install, and so on is to build translated document at least doc-admin, doc-install, and so on as far as I know..14:00
ianychoiFor releasenotes, translated horizon releasenote for one release is available.14:00
eumel8ianychoi: otherwise submit your proposal in my patch, please. I think it's easier before I'm going crazy with permanently reading this shell script ;)14:00
ianychoieumel8, I see but the file is just real life of shell script... :)14:01
eumel8ianychoi: I know, depends on time I have also no other solution for the moment. I think a ansible role is what we want at the end with all this kind of tasks14:02
ianychoieumel8, plz help how to define and develop such ansible role :) I am not still so good at them..14:04
eumel8ianychoi: maybe you want to join the OSA team. Lot's of people for help there  ;)14:06
*** jamesmcarthur has joined #openstack-i18n14:06
ianychoieumel8, thanks but for me finding my next career has more priority nowadays....14:07
eumel8ok, will close the Office Hour if there are no more suggestions14:07
eumel8#endmeeting14:07
*** openstack changes topic to "logs.openstack.org is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown."14:07
openstackMeeting ended Thu Jul 19 14:07:24 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_i18n_office_hour/2018/openstack_i18n_office_hour.2018-07-19-13.00.html14:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_office_hour/2018/openstack_i18n_office_hour.2018-07-19-13.00.txt14:07
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_i18n_office_hour/2018/openstack_i18n_office_hour.2018-07-19-13.00.log.html14:07
eumel8ianychoi: sure, just wondering you're still on search14:07
eumel8ianychoi: just another interesting platform: https://remotelist.io/14:09
ianychoieumel8, still on search and thanks a lot for sharing a link!14:11
eumel8ok, will move out from the office for today14:22
ianychoieumel8, see u later :)14:27
eumel8cu :)14:27
*** eumel8 has quit IRC14:27
jamesmcarthurianychoi: eumel8: amotoki: https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=346414:32
ianychoijamesmcarthur, https://prnt.sc/k8h177 => 65% translation were very fine by just adding <p> </p>, <a href />, and an additional "OSF" string, and so on.14:46
jamesmcarthuroh awesome :)14:47
ianychoijamesmcarthur, would you see source string parts on https://prnt.sc/k8h3f9 and https://prnt.sc/k8h3rk ? Would it be possible to divide one <ol></ol> into multiple <li><p></p></li>s ?14:51
ianychoijamesmcarthur, and.. would it be possible to add translator names in the last <h4 class="subtitle">CONTRIBUTORS</h4> or <h4 class="subtitle">TECHNICAL WRITER</h4> parts?14:52
ianychoi(Or defining one more source string part for additionally mentioning translator lists)14:52
ianychoiAnd seems that "Container technologies like..." part were not in PDF source strings and added to HTML :) That's fine.14:53
ianychoiThat's all on my analysis on new source strings on edge computing whitepaper HTML translation :)14:54
jamesmcarthurianychoi: let me take a look a the HTML14:55
ianychoijamesmcarthur, ideally it would be so nice if source string targets are strings inside <p> and </p> but if such implementation takes more time, then just diving one <ol></ol> into multiple <li><p></p></li>s is also pretty fine :) Thanks a lot for great work on translation support for HTML whitepaper stuff!14:59
jamesmcarthurOK - ianychoi: we will take care of those updates. Might take a day or so and then we will resubmit the pot files with the changes15:02
ianychoijamesmcarthur, great - thanks a lot! :)15:09
jamesmcarthurianychoi: we will add a list of translators15:09
jamesmcarthurtrying to figure out the easiest way for you all to populate that15:09
ianychoi+1 :)15:10
ianychoiReally thank u!15:10
jamesmcarthursince the pot file will be empty15:10
jamesmcarthurmaybe you could just send a list to me with the exact names and we can add in by hand?15:10
ianychoiIMO for translated guides would u just leave "TRALSLATORS: " for translators to add such parts?15:11
jamesmcarthursure, but then it would only be the translators listed in each po file15:11
jamesmcarthurIOW, when the user selects the language, it would only show the translators for that language15:12
jamesmcarthuris that ok?15:12
ianychoiYep that should be okay :) It it not a good idea to add my name to German whitepaper :)15:12
ianychois/It it/It is15:12
*** pcaruana has quit IRC15:12
jamesmcarthurlol - fair enough15:13
jamesmcarthurthank you :)15:13
ianychoiThank you too :)15:14
*** jamesmcarthur_ has quit IRC16:11
*** tesseract has quit IRC16:56
*** jamesmcarthur has quit IRC17:16
*** jamesmcarthur has joined #openstack-i18n17:42
*** jamesmcarthur has quit IRC17:42
*** jamesmcarthur has joined #openstack-i18n17:42
*** jamesmcarthur has quit IRC17:50
*** jamesmcarthur has joined #openstack-i18n17:50
*** jamesmcarthur has quit IRC17:59
*** jamesmcarthur has joined #openstack-i18n18:10
*** jamesmcarthur has quit IRC18:31
*** jamesmcarthur has joined #openstack-i18n18:35
*** itlinux has joined #openstack-i18n19:06
*** tosky has quit IRC19:16
*** jamesmcarthur has quit IRC20:01
*** jamesmcarthur has joined #openstack-i18n20:26
*** jamesmcarthur has quit IRC20:28
*** jamesmcarthur has joined #openstack-i18n20:32
*** jamesmcarthur has quit IRC20:52
*** jamesmcarthur has joined #openstack-i18n20:57
*** jamesmcarthur has quit IRC21:14
*** rcernin has joined #openstack-i18n21:58
*** itlinux has quit IRC22:22
*** jamesmcarthur has joined #openstack-i18n22:32
*** itlinux has joined #openstack-i18n22:42
*** jamesmcarthur has quit IRC22:43
*** rcernin_ has joined #openstack-i18n22:47
*** rcernin has quit IRC22:49
*** jamesmcarthur has joined #openstack-i18n22:57
*** jamesmcarthur has quit IRC23:13
*** jamesmcarthur has joined #openstack-i18n23:14
*** jamesmcarthur has quit IRC23:35
*** jamesmcarthur has joined #openstack-i18n23:41
*** jamesmcarthur has quit IRC23:41

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!