Re: rtl ltr and friends

> Hmm I did not translate code, nor did I translate function names into 
hebrew. only the explanation, and that includes the prototype.

this was just example that not all the english we want to translate.

> on RTL parsing that I displayed it (with 8859-8-i), it looked great, much better 
than mixed with english.

there are 2 issues here:
1. its true, that reading a sentence that was wrote in one lang it comfortable then reading 2.
2. there *were* logical problem regrading displaying combined langs in one html line.

as u know, times we *have to* use combined hebrew and english like on funcnames, consts, conf option, names and so on - doing the whole document rtl'ed is too simplistic solution.
my design problem with ur protos, without the principle problem of breaking the convention and uniform (that is not serious problem right now, considering the poor status of the hebrew translation), is that i *can but dont want* rtl it coz the other english protos into the translation, and with functions that wasn't translated.
it's true that i can easy chek for lang and follow the right operation, but i afraid that using future technologies for generation of the manual, this 'll cause problems.


> If you changed something in the way the pages are parsed, I guess you 
can't blame me for that...

come on... leaving with reverse english is not something that can be considered as valid default behavior.

-- 
moshe