Open Stack

Hello,

Sorry for my late reply from this thread.
I was very busy on my lots of business stuff (also dealing with some 
other I18n issues)
but I have been following the discussion on translating release notes in 
this mail thread.

Some stories were already mentioned from Akihiro, but I would like 
repeat and tell more background & details
for more translators (sometimes they might be unfamiliar with the detail 
context in the thread) to involve in the discussion.

Before OpenStack release team published release notes on 
releases.openstack.org,
release notes had been published through wiki.openstack.org, and I have 
seen that so many
I18n people were interested & participated in translating release notes 
- for example, [1].
At that time, translators focused on per-release translation.

After the transition to releases.openstack.org, translation support on 
release notes needed additional
effort, and it took about one year to support release note translation 
(from [2] to [3]).
Now I see that there are translated release notes for some projects - 
for example, Horizon [4],
but it seems that the translation participation is not rather high 
comparing to the previous period (wiki.openstack.org).

 From such experiences, in my opinion, encouraging per-release note 
translations
would be more attractive for translators to more participate in release 
note translation,
and minor embarrassing on publication would have less priority than such 
encouragement.

Developers also contribute translation, and they are able to improve 
current UI/UX for better publication,
but for the perspective from developer side, the feedback would be very 
important to precisely collect new requirements
and decide the best approach to be implemented.

Thanks a lot, Robert - for such kind asking & discussion, and I hope 
that more translators and language
coordinators will share & express their perspective and opinion not only 
in here but also through
many I18n communication channels like IRC meeting, Summit, and so on.

(By the way, would it fine for me to change the status [2] as 
"Implemented"?)


With many thanks,

/Ian

[1] https://wiki.openstack.org/wiki/ReleaseNotes/Kilo
[2] 
https://blueprints.launchpad.net/openstack-i18n/+spec/release-notes-translation
[3] 
http://lists.openstack.org/pipermail/openstack-i18n/2016-October/002502.html
[4] https://docs.openstack.org/releasenotes/horizon/index.html


Robert Simai wrote on 3/10/2017 9:40 PM:
> On Friday, 10 March 2017, 21:32:14 CET, Akihiro Motoki wrote:
>> 2017-03-10 2:13 GMT+09:00 Robert Simai <robert.simai at suse.com>:
> [...]
>
>> Have you tried sphinx actually?
>>
>> Based on what sphinx does, ja/mitaka.html will exist
>> even if the page was not translated at all.
> Good to know, thanks.
>   
>>> - fallback to the untranslated mitaka page
>>> -> if you continue to switch releases you'll stay in the untranslated
>>> versions
>>>
>>> - page exists but is untranslated
>>> -> not helpful for users
>> That's true, but translators are not supermen.
> Well, I know. And I'm also putting spare time into translations.
>
>> Do you want translators to translate all releases?
> Long story short, I just tried to express my view as I thought you had asked
> for that. If you think publishing should be based on the percentage per
> release I'm absolutely fine. We don't need to enforce anything here.
>
> [...]
>