On Mon, Sep 04, 2017 at 01:45:25PM +0800, 殷啟聰 | Kai-Chung Yan wrote:
> +1 to setting UTF-8 as default.
>
> Some Java packages that I worked with contain source files with symbols not
> recognized by compilers unless the encoding is set to UTF-8. Mostly these
> symbols are a copyright sign "©" ap
+1 to setting UTF-8 as default.
Some Java packages that I worked with contain source files with symbols not
recognized by compilers unless the encoding is set to UTF-8. Mostly these
symbols are a copyright sign "©" apprearing in the license section,
occasionally CJK letters in the author names.
]] Ivan Shmakov
> > Tollef Fog Heen writes:
> > Ivan Shmakov
> > Hans-Christoph Steiner writes:
>
> >>> Package: dpkg-dev
>
> >>> More and more packages are adding unicode files
>
> >> I assume you mean “UTF-8 filenames” here (per below), right?
>
> >>> as unicode support ha
> Tollef Fog Heen writes:
> Ivan Shmakov
> Hans-Christoph Steiner writes:
>>> Package: dpkg-dev
>>> More and more packages are adding unicode files
>> I assume you mean “UTF-8 filenames” here (per below), right?
>>> as unicode support has become more reliable and available.
]] Ivan Shmakov
> > Hans-Christoph Steiner writes:
>
> > Package: dpkg-dev
>
> > More and more packages are adding unicode files
>
> I assume you mean “UTF-8 filenames” here (per below), right?
>
> > as unicode support has become more reliable and available.
>
> What are
> Hans-Christoph Steiner writes:
> Package: dpkg-dev
> More and more packages are adding unicode files
I assume you mean “UTF-8 filenames” here (per below), right?
> as unicode support has become more reliable and available.
What are the use cases for such filenames?
Hans-Christoph Steiner writes ("make dpkg-buildpackage default locale UTF-8"):
> More and more packages are adding unicode files as unicode support has
> become more reliable and available. The package building process is not
> guaranteed to happen in a unicode locale since the Debian default loca
7 matches
Mail list logo
