On Sat, 05 Nov 2011, Bill Allombert wrote:
> Of course entities are translatable. What are you actually wanting to say ?
Well, nowadays we expect to handle translations just with PO files. And in
this context, you're expected to keep an entity between the original
string and the translated one.
"
On Fri, Nov 04, 2011 at 02:52:34PM +0100, Raphael Hertzog wrote:
> On Fri, 04 Nov 2011, Bill Allombert wrote:
> > I would suggest we use entities instead of hard-coding 'MUST NOT/SHOULD
> > NOT'.
> > This way it will be easier to generate policy document with the lower case
> > variant for people
On Fri, 04 Nov 2011, Bill Allombert wrote:
> I would suggest we use entities instead of hard-coding 'MUST NOT/SHOULD NOT'.
> This way it will be easier to generate policy document with the lower case
> variant for people who cannot read uppercase words.
Entities are not translatable. Even if there
On Fri, Nov 04, 2011 at 09:55:45AM +0900, Charles Plessy wrote:
> Package: debian-policy
> Version: 3.9.2.0
> Severity: wishlist
>
> Dear all,
>
> following our discussion at the end of October about the vocabulary used in
> the
> Policy, (20111025143614.gb14...@merveille.plessy.net), here is a
Package: debian-policy
Version: 3.9.2.0
Severity: wishlist
Dear all,
following our discussion at the end of October about the vocabulary used in the
Policy, (20111025143614.gb14...@merveille.plessy.net), here is a first pass on
Chapter 5, to use the vocabulary of RFC 2119
(http://www.ietf.org/rf
5 matches
Mail list logo
