On 13/03/2012, at 6:19 PM, BGB wrote:
> On 3/12/2012 9:01 PM, David Barbour wrote:
>>
>>
>> On Mon, Mar 12, 2012 at 8:13 PM, Julian Leviston <jul...@leviston.net> wrote:
>>
>> On 13/03/2012, at 1:21 PM, BGB wrote:
>>
>>> although theoretically possible, I wouldn't really trust not having the
>>> ability to use conventional text editors whenever need-be (or mandate use
>>> of a particular editor).
>>>
>>> for most things I am using text-based formats, including for things like
>>> world-maps and 3D models (both are based on arguably mutilated versions of
>>> other formats: Quake maps and AC3D models). the power of text is that, if
>>> by some chance someone does need to break out a text editor and edit
>>> something, the format wont hinder them from doing so.
>>
>>
>> What is "text"? Do you store your "text" in ASCII, EBCDIC, SHIFT-JIS or
>> UTF-8? If it's UTF-8, how do you use an ASCII editor to edit the UTF-8 files?
>>
>> Just saying' ;-) Hopefully you understand my point.
>>
>> You probably won't initially, so hopefully you'll meditate a bit on my
>> response without giving a knee-jerk reaction.
>>
>
> I typically work with the ASCII subset of UTF-8 (where ASCII and UTF-8 happen
> to be equivalent).
>
> most of the code is written to assume UTF-8, but languages are designed to
> not depend on any characters outside the ASCII range (leaving them purely for
> comments, and for those few people who consider using them for identifiers).
>
> EBCDIC and SHIFT-JIS are sufficiently obscure that one can generally pretend
> that they don't exist (FWIW, I don't generally support codepages either).
>
> a lot of code also tends to assume Modified UTF-8 (basically, the same
> variant of UTF-8 used by the JVM). typically, code will ignore things like
> character normalization or alternative orderings. a lot of code doesn't
> particularly know or care what the exact character encoding is.
>
> some amount of code internally uses UTF-16 as well, but this is less common
> as UTF-16 tends to eat a lot more memory (and, some code just pretends to use
> UTF-16, when really it is using UTF-8).
Maybe you entirely missed my point:
>> If it's UTF-8, how do you use an ASCII editor to edit the UTF-8 files?
>> Hopefully you understand my point.
>> You probably won't initially, so hopefully you'll meditate a bit on my
>> response without giving a knee-jerk reaction.
>
Julian
_______________________________________________
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc
