Re: Hebrew support in phpdoc

From: Date: Mon, 19 May 2003 20:08:48 +0000
Subject: Re: Hebrew support in phpdoc
References: 1  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969353661@lists.php.net to get a copy of this message
On Mon, 19 May 2003, Gabor Hojtsy wrote: > [Note: ugly subject changed ;)] > > > Changing direction is simple - it can be done in two ways: > > > > 1. <span dir="rtl">text</span> > > 2. <span DEFANGED_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... > > OK, the HTML side of it is simple. But currently we have no generic > container for example contents. They are in a <div class="php"> or in a > div with some class provided in the role="" attribute of the > programlisting. A <div class="programlisting"> class is used if no role > is present. Well, those CSS classes that already exist, can be added the property: text-align: left; And that way (so I believe) they will ALWAYS be aligned left... > > The question is what are the contents which should be ltr in the Hebrew > display? Only examples are affected? Wouldn't it be a problem that generally i am talking about those things with CODE and those weird signs before them. but every english part should be left-to-right, because that's how english is read... > English comments will be translated inside the examples to Hebrew? Or comments? as in user comments? > what to do with those parts, where a programlisting is [mis]used to > present content. This kind of usage is common in the installation part, > where it wouldn't look nice probably to have code blocks after every > sentence, so the whole explanation is put under one code block. > i totally lost you, but generally, like i said, if it's english, it's ok for it (and it is preferred that way) to be in left-to-right... > So we know that doing this in HTML is easy. The question is how to > automate it, and for what parts of the manual? well, if the code is already using some CSS, like I said in my first comment, just add the "this style is left-to-right" to the CSS class... > > Goba > -- 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."

« previous php.doc (#969353661) next »