2008/3/4, Jim Allan <[EMAIL PROTECTED]>: > > Johnny Rosenberg wrote: > > > Personally I have stopped using Arial and the other msttcorefonts since > I > > discovered that some of the characters didn't follow the UTF-8 character > > table. > > > I think you may have been confused because this seems to be to be very > bad advice. > > ALL characters in the msttcorefonts follow Unicode standards and agree > with printed Unicode tables. See http://www.unicode.org/charts/ . > > There are a few characters that appear in the Private Use Area and so > may seem non-standard. These may be what you are talking about. > > But the Private Use area is set aside by Unicode design to be used for > non-standard characters. Font designers (not just for Microsoft fonts) > often use this area for characters not found in Unicode which they wish > to use, or for variant accents and other odd characters. Characters in > the Private Use Area are supposed to be non-standard and should never be > used in normal text in any font, unless you know that the person > receiving your data has exactly the same version of the same font as you > do, or you intend your document to be published in PDS or a similar > format which will retain all font glyph information and display the > characters of the original source regardless of what fonts the viewer > has installed. > > Possibly that was your difficulty. > > Nor is there any such thing as a UTF-8 character table separate from a > plain, ordinary Unicode table, except that one could create a table > giving hex or decimal versions of the UTF-8 binary values for each > Unicode character instead of the standard Unicode values. > > > Jim Allan >
Actually I experienced some problems with Arial myself in OpenOffice.org, but when I try it now, with my other computer, there seem to be no problems any more. Strange. So I went back to the laptop and the problem still exists there. For example, the ´ is a ¥ with Arial. On this desktop PC it is a ´ no matter if I use Arial or DejaVu Sans. Strange, I wonder what could be wrong with my laptop. Nothing that is supposed to be discussed in this thread anyway. Sorry for the false alarm. J.R.
