Re: Re: Hebrew support in phpdoc

On Mon, 19 May 2003, Gabor Hojtsy wrote: > >>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... > > But we cannot autodetect what English and what is translated. This will > mean that Why don't we? Code (PHP, user notes...) comes in English (you can't translate the function names! PHP knows only english ;)) > > a) non translated pages will go out to the browser with > iso-8858-8-i but with English conetnt I thought that if the page was not translated, a copy of the English is placed instead of it? I mean, simply generated from English, and placed there? > b) English text on these pages will be RTL If I am wrong and it reads the english and enforces the hebrew properties (for no good reason...) - then yes - this will be true, I guess. But if it's ture, I can't understand the idea behind compiling a different page that is equal to a different page, instead of, for instance, include()ing the relevant /en/ page... (but that's just me...) > 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. > >>English comments will be translated inside the examples to Hebrew? Or > > > > comments? as in user comments? > > "comments inside the examples" mean PHP comments inside code examples > from the manual and not user comments. See the official code example on > http://www.php.net/manual/en/function.echo.php. So you are not > going to > translate those comments inside official code examples? > I will translate them - it is possible to read hebrew in LTR mode if it's not a complex text. Moreover, in textbooks notes in code are always displayed aligned to left, to be "English compatible", "because it's a code" > >>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... > > Ups, I guessed you know the installation parts I was referring to. See > the code usage I referenced in point c) above. That is not example code, > is text. Would you translate that? Wouldn't it be bad to show that LTR? > Well, I would translate the real text there (which is not part of the example, like: //let's connect to the db, and what is pure CODE, I'll put in CODE tags, even if the original manual page didn't do so... if it's code, it should be treated that way... > >>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... > > I have understood that, don't repeat the same thing please, please, > please.... I have underlined some problems, please concentrate on them. > ;) > 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."