On 26 August 2017 at 16:21, Björn Persson wrote:
> Tomasz Kłoczko wrote:
> > This how it IMO should be done:
> [..]
> That looks like a good plan for how large numbers of translators can
> contribute translations to many different languages.
>
> Writing the translations directly in the spec doesn
Tomasz Kłoczko wrote:
> This how it IMO should be done:
>
> 1) every release of the package to git repos should automatically
> pass them over filters extracting strings which needs to be
> translated.
>
> 2) all phrases which needs to be translated should be hold in i18n .po
> files as reference
On 25 August 2017 at 17:57, Björn Persson wrote:
> "Cheng Ye" wrote:
> > By the way, the upstream of this package provides a Chinese translation
> of the summary and translation. How to make these only visible to Chinese
> users?
>
> You can include translations in the spec with "Summary(xx):" a
On 25 August 2017 at 17:57, Björn Persson wrote:
> "Cheng Ye" wrote:
> > By the way, the upstream of this package provides a Chinese translation
> of the summary and translation. How to make these only visible to Chinese
> users?
>
> You can include translations in the spec with "Summary(xx):" a
"Cheng Ye" wrote:
> By the way, the upstream of this package provides a Chinese translation of
> the summary and translation. How to make these only visible to Chinese users?
You can include translations in the spec with "Summary(xx):" and
"%description -l xx", where "xx" is the language code. H
