| PLEX86 | ||
|
Apache unicode question 3389alex What do you mean by "use unicode characters"? Hardcoded, numeric, Unicode representation? Non-ASCII characters? And thus a number of authoring platforms, tools, etc. all with their own quirks-deficiencies-shortcuts :( Which browsers-versions. Do you really want to support every browser quirk currently known to "force" a particular rendering? "odd marks" means what? Squares? Asterisks? Platform or font subsbreastutes? Blanks? Apache unicode question 3390 Wow, so many questions. I'll try to answer most of them. First off, I neglected to mention in my original post that there didn't appear to be any... Please give us specific character encodings used (ie., charset, codepage, OS platform, etc.). These are absent from the above page, so each browser is likely to "do it's best" according to how the user has configured the browser. What do you mean by "correctly"? Do you want typographical apostrophe and quote? Just ASCII? Do you mean running the file as stored on the server through od? As delivered to some clients? What char codes does it show? Europe, The chars mentioned are rendered differently by my browser (Konqueror on Linux) in "automatic modes". In "manual" modes (ViewSet Encoding) it varies even more depending on what I select ;) Depending on the authoring tools and how they were configured and-or their default behavior, this could present problems-inconsistencies with some chars in the source files. How they will be interpreted may be a crap shoot;) There are ways to attempt to force client browsers to render them as "extended, typographical" chars, but the users' browsers may: -- use a different, specified, default charset (encoding) -- may not have an appropriate font (subsbreastute) to render them -- may simply ignore "instructions" from the server despite all your efforts -- may have a bug These and some other chars are particulary difficult to handle, especially without some MS TrueType fonts on the computer. These map on Windows into the extended ANSI range in page positions peculiar to Windows. But even the Unicode standard has trouble with these ;) I did not look, but I seem to recall some scripts running around that will "sanitize-scrub" source files looking for problematic chars and inserting the site "standard". Perl? Here's some links that may help somewhat or at least provide some ideas on how to achieve site wide consistency (without CSS). Googles: good luck, prg
|
||||
Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||