kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #03834
Re: We should decide a quoting convention...
-
To:
kicad-devel@xxxxxxxxxxxxxxx
-
From:
"Lorenzo" <lomarcan@...>
-
Date:
Wed, 23 Dec 2009 17:54:01 -0000
-
In-reply-to:
<936b14d20912230004q76212bb3n732d1b063438a052@...>
-
User-agent:
eGroups-EW/0.82
--- In kicad-devel@xxxxxxxxxxxxxxx, Manveru <manveru@...> wrote:
> New line should have loose convention, you may write \n into file, but
> remember about ignoring \r - that is for platform to platform compatibility.
This is for the container file, I agree... but INSIDE a quoted string thereis no need for this convention... and anyway IIRC even on windows a multiline editbox only gives \n
> This should work then even under Mac (Does Mac OS X change the conventionto
> unix? Or does Apple left the \r as their basic new-line marker in text
> files?).
I think that it switched to the unix way. But I remember from somewhere that instead of using unicode normalization form C uses normalizatio form D, at least in some places (file names for sure): so an 'accented a' is encodedas a a single codepoint in form C (the accented letter) while in form D isthe plain letter A codepoint and the combining accent one. It's a relatively simple table driven algorithm to convert between them, anyway (a must for every utf-8 toolkit:P)...
References