Open Stack

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
>
>