| |
In lugnet.admin.general, Selçuk Göre writes:
> Todd Lehman wrote in message ...
> > > Another thing to consider: What about letters like ç and ö like in my
> > > name?
> >
> > They're not a problem at all from an internal coding standpoint, but they
> > don't work in URLs, so the letters have to be ASCII a-z only. Your best
> > bet might be something like 'sgore'.
>
> Oh, that old, boring "sgore" again..:-( What if could manage to make my
> relaltives lego maniacs some day?..:-)
>
> Sema Gore (sister)
> Sema Gore (wife)
> Senay gore (mother)
Wow, four names in the family that all start with "se" -- excellent!
Do your mother and sister have middle or other familiar names to
distinguish between them?
> ..heheh. most probably I would prefer selcukg (auczilla nick..:-)
Well, internally, there you're "selgore", but only I see that. Externally,
you're "Selçuk G". :-)
> Anyway, I could withstand it although I would not so happy (teyyareci is
> my real life nick, although not used very very frequently). What about
> short forms of names? for example "selo" is the short form of Selçuk.
> another gray area, right?..:-)
I think that's a gray area, yeah. Thanks for the additional gray-area
examples.
> > > They are already part of code page 437, but I know they could
> > > cause some problem here or there.
> >
> > What is code page 437? Is that some Microshaft thing? (I seem to
> > remember something like this back from my NT/army days.) The important
> > thing,really, is that ç and ö are part of ISO-8859-1 (a real standard),
> > but not part of ASCII (another real standard). Microshaft code pages
> > aren't real standards.
>
> I'm not very deep in the subject, but Is ASCII has 128 or 256 characters?
ASCII is 7-bit, and it's either 127 or 128 characters, I forget which.
> If second is true, code page 437 is the default codepage (US) for IBM
> compatible PC's and exactly same as ASCII, and contains many specialized
> characters like ç and ö. If ASCII has only 128 characters, then first 128
> characters of the code page 437 exactly coincided with ASCII (as well as
> other code pages since only differences could be found through latter 128
> characters). Those are all from old days of MS/IBM-PC DOS era.
>
> As far as I know, ISO 8859-1 is for western languages only, and the
> standard that covers all the Turkish alphabet is ISO 8859-9 (according
> to Netscape communicator)
Yeah, hopefully someday it'll all be obsoleted by Unicode, if Unicode works
out as perfectly as it was planned to. BTW, when you use ç and ö from the
ISO-8859-1 character set in posts, are those the accurate Turkish character
representations, just happening to coincide with western languages, or are
they just close approximations?
Anyway, URLs containing non-ASCII characters (and some ASCII characters too
of course, like + and % and space, etc.) have to be specially encoded. So
even if you had 'selçukg' as a member-ID and it appeared encoded in a URL
like so:
http://www.lugnet.com/people/sel%E7ukg/
I'm not even sure if %E7 always is assumed to decode to ç -- it *might*
depend on the particular language someone is running. Anyway, for a number
of reasons, the least of which is readability, it's good idea to avoid %'s
in URLs if at all possible, unless they're localized to one country (which
these aren't).
> :-D Member ID# could serve this well. In a science fiction novel that
> I've read, smaller social security number (tattooed on peoples skin)
> means the higher social carrier..:-)
Keep the gray-area examples coming! :) We get enough of those and ID#'s
will be the only logical choice.
--Todd
|
|
Message has 1 Reply:
Message is in Reply To:
112 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
