Wednesday, 2017-05-03

*** ykatabam1 has quit IRC01:03
*** ykatabam has joined #openstack-i18n01:17
*** epico has joined #openstack-i18n02:34
*** aeng has quit IRC04:03
*** aeng has joined #openstack-i18n04:20
*** aeng has quit IRC05:08
*** ykatabam has quit IRC05:15
*** aeng has joined #openstack-i18n05:21
*** pcaruana has joined #openstack-i18n06:27
*** ykatabam has joined #openstack-i18n07:33
*** epico has quit IRC07:37
*** epico has joined #openstack-i18n07:39
*** steveg_afk has joined #openstack-i18n09:29
*** tesseract has joined #openstack-i18n09:56
*** epico has quit IRC10:02
*** epico has joined #openstack-i18n10:07
*** epico has quit IRC11:08
*** steveg_afk has quit IRC11:32
*** ykatabam has quit IRC11:52
*** pcaruana has quit IRC11:53
*** pcaruana has joined #openstack-i18n11:57
*** steveg_afk has joined #openstack-i18n13:10
*** steveg_afk has quit IRC13:57
*** amotoki has joined #openstack-i18n14:26
*** pcaruana has quit IRC16:24
*** tesseract has quit IRC16:38
*** steveg_afk has joined #openstack-i18n18:14
-openstackstatus- NOTICE: Gerrit on review.openstack.org is being restarted to accomodate a memory leak in Gerrit. Service should return shortly.18:52
*** steveg_afk has quit IRC18:55
*** openstackgerrit has joined #openstack-i18n19:35
openstackgerritMerged openstack/i18n-specs master: Add description in README with template  https://review.openstack.org/41314619:35
*** steveg_afk has joined #openstack-i18n19:50
*** ykatabam has joined #openstack-i18n22:13
*** ediardo_ has joined #openstack-i18n22:24
ianychoiamotoki, good morning! Can I discuss https://review.openstack.org/#/c/454663/ for i18n.pot naming? Andreas suggested to use i18n for i18n-guide and change i18n.po(t) to like i18n-glossary.po(t) for the consistency in infrastructure sync jobs defined in openstack-infra/project-config22:24
ianychoiamotoki, so I now would like to change from i18n.po(t) to i18n-glossary.po(t) for glossary file naming. Is there a specific reason why the name was finally chosen as i18n.pot for glossary? If not, I think I would like to go forward.22:26
amotokiianychoi: hi22:28
amotokiianychoi: I am not sure what is the rational22:28
*** ediardo has quit IRC22:28
ianychoiamotoki, hi. The rational for using "i18n" for i18n guide?22:28
amotokiianychoi: previously when we introduced the glossary to the i18n repo, he suggested to use i18n.po as the glossary po file22:28
amotokialthough I was against it.22:28
*** ediardo_ is now known as ediardo22:29
ianychoiamotoki, aha. https://review.openstack.org/#/c/461924/ -> you can see the comment from Andreas22:29
amotokiianychoi: about naming of po(t) in a repository potentially with multiple pot files22:30
amotokiianychoi: what happens if we have python codes in a same repo? rename again?22:30
amotokiI am not sure 'i18n' in 'i18n' project is clear to translators on Zanata as well.22:31
ianychoiamotoki, hmm thanks - good suggestion22:31
ianychoiamotoki, thanks. I might need to discuss with Andreas again by taking an example of heat repository - heat translation (Python code) itself and heat install-tutorial documentation22:31
ianychoiThen I think we need to define naming policy for multiple po(t) files in the same repository22:32
ianychoiIt makes sense?22:32
amotokisounds good22:32
ianychoiThanks :) Have a good day!22:33
amotokihopefully we have some guideline on naming po(t) file for documentation which exist on a regular repo (not doc repo)22:33
amotokiIf andreas and all think i18n repo is a doc repo, 'i18n' for i18n guide sounds reasonable to me.22:34
ianychoiYep reasonable - then we consider Zanata projects the same as repository and Zanata documents the same as different resources22:35
ianychoiFor this case, then changing i18n.po(t) to i18n-glossary.po(t) is okay?22:36
amotokior just glossary.po(t)22:37
ianychoiI see :)22:38
amotokiit is under 'i18n' repo/zanata project, so it is clear enough :)22:38
ianychoi+1 :)22:38

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