Re: cvs: phpdoc / Makefile.in

On Mon, 19 May 2003, Gabor Hojtsy wrote: > >>As discussed with Friedhelm, there were no test files on his server to > >>have a meta http-equiv with iso-8859-8-i charset specified. This would > >>work with Mozilla and Konqueror. Does anybody tested it with IE? I have > >>no IE, I have linux ;) > > > > OK, I am officially confused. I have just tested the following: > > <DEFANGED_meta http-equiv="Content-Type" content="text/html; > > charset=iso-8859-8-i" /> > > > > In this URL: http://shimi.staff.fresh.co.il/chat/ > > > > I have changed the encoding in Mozilla (Firebird) and in IE to Turkish. > > Then I browsed to this page. Encoding changed automatically to iso-8859-8-i. > > I saw Hebrew right. > > > > Perhaps the problem with windows-1255 on the content-type equivalents is > > that... windows-1255 is not actually the standard ? I don't care :) Is it > > possible to use the line I mentioned above? I have understood it is valid > > HTML... > > Seems like we have found a solution for the charset question which will > work and is standard. Wow! Then will come the direction question, how it > will be possible to mark direction to be ltr on English content. > > Goba Changing direction is simple - it can be done in two ways: 1. <span dir="rtl">text</span> 2. <span style="CSSstyle">text</span> and in the CSS page, something like: .CSSstyle { text-align: right; } (and you can of course use the corresponding "ltr" and "left" (CSS) to switch from left-to-right and right-to-left inside a document) at any case, in hebrew (and arabic, and all the rest of RTL languages), the whole page would look nicer (more readable) if completely aligned right-to-left with <html dir="rtl">, and only rendered LTR on the non-RTL parts of it... > > > -- Best regards, Shimi ---- "Outlook is a massive flaming horrid blatant security violation, which also happens to be a mail reader." "Sure UNIX is user friendly; it's just picky about who its friends are."