Re: Re: Hebrew support in phpdoc

> > c) Code blocks used for explanation will be LTR even if > > translated [eg. > > http://www.php.net/manual/en/install.macosx.php] > > > > Right, but since they *are* code blocks, they have to be LTR, because > otherwise they'll not be readable (for instance, --with-mysql will become > with-mysql-- and that's really not good...). If we translate something > there, it's just the title, and since it's one non complicated line, it > is... bearable. Preferred to be that way rather than having the whole code > RTL. > > This raises another point which I've noticed while going over my > translated page. Sometimes inside the Hebrew explanation, we have to give > an example of a configure option (like --with-mysql=[DIR]). And the > phenomenon I talked about in the past paragraph - happens there. See: > http://shimi.staff.fresh.co.il/ref.mysql.html (and set your > browser to RTL) > See what happens. I guess we need the <span> thingie over there too :( > I wondered if all those <option> and <literal> tags in the XML are also > translated through some CSS. If the answer is yes, this is not a > problem... for the solution I've already made. > We're going to face the same problem in the Arabic version too, all must-stay-english parts should be either rewritten in reverse against any non-alphabet charachters or use sthg like <span dir=ltr>. I suggesst using some xml directive which forces generation to add the suitable ltr mark, or I dunno if there's another solution.