Open Stack

Thanks Alex,

2016-03-03 6:40 GMT+09:00 Alex Eng <aeng at redhat.com>:
>> * is there any documentation describing this behavior?
>
> Not for po file format. (Sorry for our lack of documentation, we will
> include that in our doc)

No problem. We can gradually improve the documentation :)

>> * can we use this feature for per-language? We are now discussing to
>> add a note per language.
>
> Not by using upload of po/cvs file.
> But if the glossary is created in Zanata (ver 3.8), then we support comment
> per language.

The feature sounds nice. I hope we can leverage the feature soon.

>> * can we have multiple comments per entry?
>
> Not at this stage.
>

>>   If we need a long description, I would like to wrap lines.
>> --
>> #  this will be ignored
>> #. Only this will be stored
>> #. in description field
>> #: this will be ignored
>> #, this will be ignored
>> msgid "RPM"
>> msgstr "alex here"
>> ---
>
>
> The idea of glossary is normally short sentence(1 or 2 words).
> And ideally it would be short description as well. Our field for description
> is a 1 liner.
> But if there's a request for multiple line support, feel free to let us
> know.

I generally agree with you.
Each entry of glossary is short (1 or 2 words).
Description in my mind can be used, for example, to describe when we
should use some word
and when we should use another work for translation. We would like to
describe the contextual information.

However, I don't think we need to support multiple lines at the moment.
Requirements are too ambiguous.

I just tried to clarify what we can and what cannot.
In the current Japanese glossary, the longest note is around 90 Japanese chars
(one Japanese characters can be counted as almost two ASCII characters).
If we need longer information, we can use URL instead.

thanks,
Akihiro

>
>
> ---------------------------------------------
>
> Alex Eng
> Senior Software Engineer
> Globalisation Tools Engineering
> DID: +61 3514 8262
> Mobile: +614 2335 3457
>
> Red Hat, Asia-Pacific Pty Ltd
> Level 1, 193 North Quay
> Brisbane 4000
> Office: +61 7 3514 8100
> Fax: +61 7 3514 8199
> Website: www.redhat.com
>
> On Wed, Mar 2, 2016 at 8:04 PM, Akihiro Motoki <amotoki at gmail.com> wrote:
>>
>> Thanks Alex and Daisy,
>>
>> I have several questions.
>>
>> * is there any documentation describing this behavior?
>> * can we use this feature for per-language? We are now discussing to
>> add a note per language.
>> * can we have multiple comments per entry?
>>   If we need a long description, I would like to wrap lines.
>> --
>> #  this will be ignored
>> #. Only this will be stored
>> #. in description field
>> #: this will be ignored
>> #, this will be ignored
>> msgid "RPM"
>> msgstr "alex here"
>> ---
>>
>> Akihiro
>>
>> 2016-03-02 7:00 GMT+09:00 Alex Eng <aeng at redhat.com>:
>> > Daisy,
>> >
>> > If you're importing po files, the only field it will populate is the
>> > "description" field which extract from comment in message.
>> > There's no "pos" related field in po file.
>> >
>> > See the attached file.
>> >
>> >
>> > ---------------------------------------------
>> >
>> > Alex Eng
>> > Senior Software Engineer
>> > Globalisation Tools Engineering
>> > DID: +61 3514 8262
>> > Mobile: +614 2335 3457
>> >
>> > Red Hat, Asia-Pacific Pty Ltd
>> > Level 1, 193 North Quay
>> > Brisbane 4000
>> > Office: +61 7 3514 8100
>> > Fax: +61 7 3514 8199
>> > Website: www.redhat.com
>> >
>> > On Tue, Mar 1, 2016 at 6:05 PM, Ying Chun Guo <guoyingc at cn.ibm.com>
>> > wrote:
>> >>
>> >> Thank you for the information, Alex.
>> >> I know Zanata allows to import glossaries from CSV and po files.
>> >> I can see a sample of CSV file, with "description" and "pos" field[1].
>> >> Can you provide us a sample of po file, with "description" and "pos"
>> >> field
>> >> for an entry ?
>> >>
>> >> Best regards
>> >> Ying Chun Guo (Daisy)
>> >> [1]
>> >>
>> >> http://docs.zanata.org/en/release/user-guide/glossary/upload-glossaries/
>> >>
>> >>
>> >> Alex Eng <aeng at redhat.com> wrote on 2016/02/29 05:58:23:
>> >>
>> >> > From: Alex Eng <aeng at redhat.com>
>> >> > To: "Kato, Tomoyuki" <kato.tomoyuki at jp.fujitsu.com>
>> >> > Cc: Akihiro Motoki <amotoki at gmail.com>, Ying Chun Guo/China/
>> >> > IBM at IBMCN, Openstack-i18n <openstack-i18n at lists.openstack.org>
>> >> > Date: 2016/02/29 05:59
>> >> > Subject: Re: [Openstack-i18n] To language team coordinators: get
>> >> > ready for Mitaka translation
>> >> >
>> >>
>> >> > On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki
>> >> > <kato.tomoyuki at jp.fujitsu.com
>> >> > > wrote:
>> >>
>> >> > > Beyond this, the current format of PO file for the glossary lacks
>> >> > > an
>> >> > > essential feature as I described before. There is no way to
>> >> > > describe
>> >> > > the
>> >> > > context.
>> >> > > I wonder how the glossary help translations without the contextual
>> >> > > information.
>> >> > > As a result, Japanese team is forced to describe contextual
>> >> > > information
>> >> > > in translated strings.
>> >> > > This is the reason we preferred to Wiki style glossary.
>> >> > >
>> >> > > From the above observation, does it sound a good option to clear
>> >> > > the
>> >> > > whole
>> >> > > entry of Zanata glossary of a specific language?
>> >> >
>> >> > FYI, as of Zanata 3.8, we support same source string with unique
>> >> > "description" and "pos" field for each glossary entry.
>> >> > This will help translator with more context information and able to
>> >> > have similar string with different context.
>> >> >
>> >> >
>> >>
>> >> >
>> >> > ---------------------------------------------
>> >> >
>> >> > Alex Eng
>> >> > Senior Software Engineer
>> >> > Globalisation Tools Engineering
>> >> > DID: +61 3514 8262
>> >> > Mobile: +614 2335 3457
>> >> >
>> >> > Red Hat, Asia-Pacific Pty Ltd
>> >> > Level 1, 193 North Quay
>> >> > Brisbane 4000
>> >> > Office: +61 7 3514 8100
>> >> > Fax: +61 7 3514 8199
>> >> > Website: www.redhat.com
>> >
>> >
>
>