On Mon, 2012-12-10 at 13:15 -0500, Shaun McCance wrote:
But if we're going to write guidelines, here's my semi-professinal
opinion:
* Using hyphens instead of dashes for parenthetical text is awful.
Using unspaced hyphens-like this-is downright confusing.
* I'm old and I like unspaced
Philip Withnall phi...@tecnocode.co.uk a écrit:
Are there any reasons against putting UTF-8 characters in the source
code (which weren’t covered in my blog post)?
Sorry, but which blog post?
--
Dodji
___
desktop-devel-list mailing
On Wed, 2012-12-12 at 17:35 +0100, Dodji Seketeli wrote:
Philip Withnall phi...@tecnocode.co.uk a écrit:
Are there any reasons against putting UTF-8 characters in the source
code (which weren’t covered in my blog post)?
Sorry, but which blog post?
This one, which I linked to earlier:
Philip Withnall phi...@tecnocode.co.uk a écrit:
On Wed, 2012-12-12 at 17:35 +0100, Dodji Seketeli wrote:
Philip Withnall phi...@tecnocode.co.uk a écrit:
Are there any reasons against putting UTF-8 characters in the source
code (which weren’t covered in my blog post)?
Sorry, but which
Le mardi 11 décembre 2012 à 08:49 +0700, Nguyen Thai Ngoc Duy a écrit :
On Tue, Dec 11, 2012 at 12:28 AM, Philip Withnall
phi...@tecnocode.co.uk wrote:
Creating and maintaining an en_US locale which is identical to the C
locale apart from its use of UTF-8 would be a huge amount of effort for
On Tue, Dec 11, 2012 at 5:36 PM, Milan Bouchet-Valat nalimi...@club.fr wrote:
Le mardi 11 décembre 2012 à 08:49 +0700, Nguyen Thai Ngoc Duy a écrit :
On Tue, Dec 11, 2012 at 12:28 AM, Philip Withnall
phi...@tecnocode.co.uk wrote:
Creating and maintaining an en_US locale which is identical to
On Mon, 2012-12-10 at 13:15 -0500, Shaun McCance wrote:
* Unspaced en-dashes are for indicating ranges. We should use those
too, though the hyphen isn't quite as ugly when misused in this case.
Since this one should be fairly uncontroversial, I’ve added it to the
wiki page with the note that
Philip Withnall wrote:
I’ve created https://live.gnome.org/GnomeGoals/UnicodeUsage which I
think covers everything discussed in this thread so far. Please feel
free to add further suggestions to it, or move things from the
‘discussion’ to the ‘agreed’ list.
Looks good. The only thing I’d like
On Mon, 2012-12-10 at 12:50 +0100, Robin Stocker wrote:
Philip Withnall wrote:
I’ve created https://live.gnome.org/GnomeGoals/UnicodeUsage which I
think covers everything discussed in this thread so far. Please feel
free to add further suggestions to it, or move things from the
On 12-12-10 09:57 AM, Philip Withnall wrote:
Disclaimer: I’m en_GB. I’m not entirely sure that en_GB speakers should
be deciding the style to use in the C locale, given that manuals of
style differ between the UK and the US.
You must mean en_US. The C locale should not have unicode in it.
On Mon, 2012-12-10 at 10:10 -0500, Pat Suwalski wrote:
On 12-12-10 09:57 AM, Philip Withnall wrote:
Disclaimer: I’m en_GB. I’m not entirely sure that en_GB speakers should
be deciding the style to use in the C locale, given that manuals of
style differ between the UK and the US.
You must
On Mon, Dec 10, 2012 at 11:08 PM, Philip Withnall
phi...@tecnocode.co.uk wrote:
On Mon, 2012-12-10 at 10:10 -0500, Pat Suwalski wrote:
On 12-12-10 09:57 AM, Philip Withnall wrote:
Disclaimer: I’m en_GB. I’m not entirely sure that en_GB speakers should
be deciding the style to use in the C
On Mon, 2012-12-10 at 23:23 +0700, Nguyen Thai Ngoc Duy wrote:
On Mon, Dec 10, 2012 at 11:08 PM, Philip Withnall
phi...@tecnocode.co.uk wrote:
On Mon, 2012-12-10 at 10:10 -0500, Pat Suwalski wrote:
On 12-12-10 09:57 AM, Philip Withnall wrote:
Disclaimer: I’m en_GB. I’m not entirely sure
On Mon, 2012-12-10 at 12:50 +0100, Robin Stocker wrote:
Philip Withnall wrote:
I’ve created https://live.gnome.org/GnomeGoals/UnicodeUsage which I
think covers everything discussed in this thread so far. Please feel
free to add further suggestions to it, or move things from the
On Mon, 2012-12-10 at 17:28 +, Philip Withnall wrote:
Are there any reasons against putting UTF-8 characters in the source
code (which weren’t covered in my blog post)?
You can put UTF-8 in the source code, and GCC understands it just fine.
TL;DR: It's 2012. The compiler understands UTF-8 and defaults to it.
Use it :)
As I discovered recently, gjs does not like Unicode characters in string
literals.
Cheers,
Debarshi
--
There are two hard problems in computer science: cache invalidation, naming
things and off-by-one errors.
On Mon, 2012-12-10 at 19:07 +, Debarshi Ray wrote:
TL;DR: It's 2012. The compiler understands UTF-8 and defaults to it.
Use it :)
As I discovered recently, gjs does not like Unicode characters in string
literals.
You are likely referring to:
Nope. Try it yourself. Put a UTF-8 literal in an imported source file, and
then try to use Unicode literals for the character. It interprets the UTF-8
wrong. I'm quite sure this is a bug in our importer script, treating
everything as UTF-16.
On Mon, Dec 10, 2012 at 2:11 PM, Colin Walters
You are likely referring to:
https://bugzilla.gnome.org/show_bug.cgi?id=680730
Actually I was referring to https://bugzilla.gnome.org/show_bug.cgi?id=689601
Cheers,
Debarshi
--
There are two hard problems in computer science: cache invalidation, naming
things and off-by-one errors.
On Tue, Dec 11, 2012 at 12:28 AM, Philip Withnall
phi...@tecnocode.co.uk wrote:
Creating and maintaining an en_US locale which is identical to the C
locale apart from its use of UTF-8 would be a huge amount of effort for
no benefit (that I know of; please correct me if I’m wrong).
Updating C
20 matches
Mail list logo
