Re: [Quilt-dev] Quilt 0.65 coming soon

[Jean Delvare]

Hi Andreas, Yasushi,

On Wed, 2 Nov 2016 19:03:58 +0100, Andreas Grünbacher wrote:
> 2016-11-02 17:26 GMT+01:00 Yasushi SHOJI <address@hidden>:
> > On Tue, Nov 1, 2016 at 7:07 PM, Jean Delvare <address@hidden> wrote:
> > [...]
> >> --charset
> >>         Specify a particular message encoding on systems which don't use
> >>         UTF-8 or ISO-8859-15. This character encoding must match the one
> >>         used in the patches.
> >>
> >> Are we good with this?
> >
> > Yes.
> >
> > What I'm not sure is that UTF-8 is an encoding but used at "charset".
> > When "UTF-8" is used in the content-type header line, does it mean
> > the message used UCS, is the "charset" header used for
> > encodings, or is charset and encoding interchangeable here?

I am well aware that character encoding and character set are different
things. Technically UTF-8 is a character encoding, however it implies a
character set (UCS.) Conversely, ISO-8859-15 is a character set, but in
this context it implies an encoding (or actually a lack thereof.) In
practice both terms appear as interchangeable, and "charset" seems to be
a commonly accepted shortcut to designate them. For example in HTML the
Content-Type header uses a "charset" attribute to designate the
character set and encoding. Exactly as this option is doing.

> > If we align the name and the description:
> >
> > Specify a character set for the messages on systems which don't use
> > UTF-8 or ISO-8859-15.  The specified character set must match...
> >
> > But I like the original better. ;-)

And so do I. We could go with "Specify a character set and encoding..."
but I prefer the option description to be concise and clear even if not
technically perfect. The user can still search for all of "character",
"set", "encoding" and "charset" and find this option in all cases.

> In any case, we should at least go with either "character encoding" or
> "character set" in both sentences. The parameter defines both the
> character set and the encoding.

Exactly. So let's stick to my proposal. I don't want to delay the
release any further to debate the exact wording of the description of
an option which has stayed undocumented for a decade without anyone
noticing or caring ;-)

I'm committing my patch with now, together with a French translation
update. It would be great if we can get other translation updates
quickly so that I can release quilt 0.65 this week.

Thanks,
-- 
Jean Delvare
SUSE L3 Support