08:00:31 #startmeeting OpenStack I18n Meeting 08:00:32 Meeting started Thu Apr 16 08:00:31 2015 UTC and is due to finish in 60 minutes. The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:36 The meeting name has been set to 'openstack_i18n_meeting' 08:00:51 hello all :) 08:00:56 Hello 08:00:59 * AJaeger waves 08:00:59 Hello 08:01:03 Hello 08:01:10 hi! 08:01:15 Hi, loquacities 08:01:19 OK. Let's start. 08:01:24 hi Daisy :) 08:01:32 #topic rst document translation discussion with doc team 08:01:48 Welcome AJaeger and loquacities from doc team. 08:01:54 * loquacities waves 08:02:02 And welcome ujuc_ from Korean team and Fdot_ from French team. 08:02:13 I'm representative of Chinese translation team. 08:02:32 epico is from Chinese too. 08:03:01 * AJaeger does the odd bit of German translation (10 strings this release only ;) 08:03:23 ujuc_ and Fdot_ : do you need a background introduction of switching to rst document ? 08:03:47 Yes, AJaeger is from German team. 08:04:02 Daisy: that's ok :) 08:04:17 that's ok too. 08:04:30 So you understand what we are talking about. 08:04:38 I have talked about it with gpocentek :) 08:04:53 from doc team 08:04:53 There have been several mails going back and through in our mailing list. 08:04:53 Fdot_, yeah, gpocentek is an RST expert ;) 08:05:27 So fristly, AJaeger , I would like to make sure the current doc toolchain could support our future improvement. 08:05:44 Let's use a simple example. 08:06:19 If I want to change :: at the end of an sentence to :, and change back, with auto tool, which files I could change ? 08:06:54 I mean, before uploading, I change :: to :, and after downloading, I change : to :: 08:07:00 It's the simplest case. 08:07:01 We have tools/generatepot-rst.sh that creates the po files 08:07:16 And we can add transformations there any time 08:07:30 can you share the link ? 08:07:37 second... 08:07:59 http://git.openstack.org/cgit/openstack/openstack-manuals/tree/tools/generatepot-rst.sh 08:08:41 and for downloading, can do this either as part of the building process - see https://review.openstack.org/162424 08:09:15 or as part of the infra scripts http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/propose_translation_update_manuals.sh 08:10:04 But we have to be clever here, not every ":" should be converted to "::" etc. 08:10:21 ^^ that's what i was thinking 08:10:29 So, the logic there needs to search for the original string and see whether we have "original::" and only then do the transformation 08:10:32 Oh ? I didn't notice the exceptions while I was investigating the user guides. 08:10:53 Only :: at the end of every string 08:11:01 should be changed. 08:11:04 Is that correct ? 08:11:16 All :: at the end of the source strings 08:12:07 If you want to change those, you would change existing "::" in the source before uploading to ":" and then convert those translated strings that originally had a "::" back. 08:12:55 AJaeger: I don't quite understand why use :: ? 08:13:18 Daisy, I don't understand your question 08:13:48 Sorry 08:13:56 The old source string in DocBook is: 08:14:08 "To perform a hard reboot, pass the --hard parameter, as follows:" 08:14:17 The new source strings in RST is: 08:14:26 "To perform a hard reboot, pass the ``--hard`` parameter, as follows::" 08:14:32 Why this kind of changes happen ? 08:14:40 http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/user-guides/source/locale/user-guides.pot#n5497 08:15:06 Daisy, the "::" is RST markup to have the text that *follows* written as code. 08:15:07 this? 08:15:23 So, if the next line is for example a config file, we use "::" 08:15:34 IF the next time is some descriptive text, it would be a single ":" 08:16:14 oh. Then it's easy to convert :: to :, but it's hard to convert back. 08:16:50 I understand. Thank you, AJaeger 08:17:03 Daisy, you need to check first the original string, should be a simple lookup. 08:17:13 ok. Yes. 08:17:20 Thank you. 08:18:29 So based on AJaeger 's answers, I think, we could make the improvement if we want to in the future, by updating some scripts. But the logic is not easy, because when converting back, the original string need to be tested. 08:19:12 Let's move to next. 08:19:28 ok 08:19:31 https://wiki.openstack.org/wiki/I18nTeam/rst-markups 08:20:00 This page lists some markups in RST. 08:20:03 http://lists.openstack.org/pipermail/openstack-docs/2015-April/006348.html 08:20:32 This email contains more markups Olga Gusarenko added. 08:20:46 http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/user-guides/source/locale/user-guides.pot 08:20:55 This is the new pot file. 08:21:28 ujuc_ and Fdot_ : please take a look at these markups and the new pot file, and let us know if you have any concerns. 08:21:45 daisy ok :) 08:21:51 ok 08:22:17 AJaeger: :guilabel:`tab` 08:22:26 I imported the existing translations for End User Guide and Admin User Guide into the user-guides resource and also did some transformations, so we had 38 % of Japanese translated directly 08:22:28 In this case, shall we translate tab ? 08:23:13 shall we translate *tab* into the local language as to :guilabel:`tab` ? 08:23:49 "tab" might be the label in Horizon, so it needs to be translated. 08:24:09 That was the case before already, just it was tab or somethign similar 08:24:37 ok. 08:25:19 Then how about this one: :term:`glossterm_name` ? 08:25:43 do we need to translate *glossterm_name* ? 08:26:15 That'S a reference to the glossary 08:26:29 It needs to match the glossary entry - like it did before 08:27:01 So, if you translate "Compute" as key in the glossary to "Berechnen", then you need to translate the term here as well - like previously 08:27:02 Now we don't have glossary translated yet. 08:27:35 if the glossary is translated in the future, *glossterm_name* should be translated here. 08:27:53 Example: the Japanese team has 89 % of glossary translated 08:28:04 Daisy, correct. 08:28:09 ok 08:28:42 I think :menuselection:`Start > Programs` should be translated, but I want to check with you, AJaeger . 08:29:00 Daisy, whenever you come about these questions in the future, feel free to ask on openstack-docs mailing list 08:29:24 +1 08:29:25 Indeed, Daisy, those need to be translated the same way as it is in the GUI like horizon 08:29:43 Ok. I want to summarize them together, so the new comers won't bother you those questions. 08:30:16 Daisy, sure! Document what you learn and ask again for feedback, we happily review. 08:30:46 In DocBook, XML tags are clearly marked. Translators don't need to bother which should translate, which should not. RST is different way. 08:30:58 I agree it's important to know where translations need to match - like the glossary or the UI. 08:31:36 Yes, DocBook XML tags can be easily identified. But don't you translate glossterm already? 08:32:12 Not all languages translate glossary. 08:32:43 ok - but those that do have to keep this in mind already today 08:33:18 Yes, agree. I will document these down in that wiki page. 08:34:04 Thanks, Daisy! 08:34:15 ujuc_ and Fdot_ : any questions from you ? 08:34:30 Now I see why a special translators RST cheat sheet is needed 08:34:42 yes, it's trickier than i realised! 08:34:49 Daisy: not for me 08:35:36 no ~ 08:36:08 AJaeger: while translating, translators need to understand the meaning. This will help them translate. That's why I ask a lot of silly questions to you. 08:36:43 Daisy, those are no silly questions. 08:37:04 Daisy: i am in australia, and will make sure i am in #openstack-translation for you, so you can ask questions 08:37:07 The implications of different markup for translation was not that clear to me before, so your questions helped me to learn as well 08:37:12 Fdot_ and ujuc_ : you are OK to the rst document conversion now ? 08:37:44 Thank you, loquacities 08:37:52 no problem 08:37:54 Daisy: ok for me 08:38:06 Thank you, Fdot_ 08:38:15 ko 08:38:23 Thank you, ujuc_ 08:38:51 I'm fine too. I will continue to improve the translators cheat sheet. 08:39:07 Great! 08:39:12 that's great, Daisy :) 08:39:26 If you meet with new mark ups, AJaeger, please add to the cheat sheet. 08:39:43 Same to you, loquacities, Fdot and ujuc_ . 08:39:57 will do :) 08:39:58 Daisy, will keep an eye out 08:39:59 It will help the new comers easily to understand the situation. 08:40:08 Ok. great ! 08:40:23 any more questions? comments ? 08:40:41 i think i understand the issues better now, so thank you :) 08:40:48 So, do I - thanks! 08:41:06 Thank you, AJaeger and loquacities to come. 08:41:11 most welcome 08:41:24 We will move to next topic. 08:41:27 Daisy, feel free to invite us again any time you have doc questions. 08:41:27 #topic Final push on Horizon translation 08:41:35 sure, AJaeger . I will. 08:41:59 I will catch you in IRC. I will bother you too, loquacities, if i cannot find AJaeger . 08:42:20 no problem at all :) 08:42:23 You're welcome! 08:42:28 amotoki sent email to our mailing list. 08:42:29 i am probably in a better time zone for you, too ;) 08:42:45 Horzion is string freeze now. 08:42:58 The date to push Horizon translation is April 23. 08:43:11 So we have to finish them by April 22. 08:43:19 I see most languages have good progress. 08:43:31 Just two languages might have trouble. 08:43:59 Spanish and Polish 08:44:16 I will broadcast the email to a more broad mailing list and get more people's help. 08:44:37 That's all for this topic. 08:44:47 #topic Open discussions 08:45:09 Any topics to talk ? 08:45:40 i not 08:45:48 Thank you, ujuc_ 08:45:57 if no, I will close the meeting. 08:46:25 ok. Let's close it. 08:46:30 Thank you all for attending. 08:46:32 thanks Daisy :) 08:46:39 thank you, loquacities 08:46:55 #endmeeting