On 15/11/2004, at 15:32, Tzafrir Cohen wrote:
What charset do you use?
ISO-8859-8 includes none of the special bidi chars. cp1255 contains
only
LRM and RLM . UTF-8 has them all.
OpenOffice uses Unicode internally. Sometimes it won't function
properly when a user attempts to run it as a non-unicod
Tzafir Cohen wrote:
"ISO-8859-8 includes none of the special bidi chars."
This is true or not depending on the version of ISO-8859-8 that you
consider. A relatively recent update (but still dating several years
back) added LRM and RLM to ISO-8859-8.
Agents, of course, may implement the older
On Mon, 15 Nov 2004, Tzafrir Cohen wrote:
> On Mon, Nov 15, 2004 at 02:46:28PM +0200, Micha Feigin wrote:
> > At Sun, 31 Oct 2004 22:27:12 +0200,
> > Amit Aronovitch wrote:
> > >
> > > First of all, thanks Tzafrir - I was not aware that the lyx and SI
> > > variants had any bidi chars in them
>
On Mon, Nov 15, 2004 at 02:46:28PM +0200, Micha Feigin wrote:
> At Sun, 31 Oct 2004 22:27:12 +0200,
> Amit Aronovitch wrote:
> >
> > First of all, thanks Tzafrir - I was not aware that the lyx and SI
> > variants had any bidi chars in them
> > (I do remember googlin and greppin around before star
Micha Feigin wrote:
Also, what is the difference between all of these? Mainly LRE vs. LRO are
puzzling.
I can't explain it in details without referring you to the full Unicode
annex dealing with BiDi. Since there is no reason for you to fully read
and understand the 20 something points of the
At Sun, 31 Oct 2004 22:27:12 +0200,
Amit Aronovitch wrote:
>
> First of all, thanks Tzafrir - I was not aware that the lyx and SI
> variants had any bidi chars in them
> (I do remember googlin and greppin around before starting to mess with
> symbol files - probably did not do that very well - s
Hi Shosh,
Note that as of Monday this week we migrated the Hebrew OpenOffice
mailing list from majordomo to mailman and we now have archives on-site.
There are still a few glitches, like [OOo-H] was changed to [Hebrew] but
we'll straighten those out. Thanks for your patience.
- yba
On Tue, 9 No
On 01/11/2004, at 09:30, Tzafrir Cohen wrote:
As for a long-term solution: This has just been a long thread about
this
in the OOo-il mailing list. Unfortunately I can't find any up-to-date
online archive of that list. I can mail you my OOo mbox, if you want.
Here it is:
http://article.gmane.org/gm
On Sun, Oct 31, 2004 at 10:19:40PM +0200, Micha Feigin wrote:
> I still think that this is the wrong approach, even if it is the easiest. I
> think that directionality should be taken from the keymap and not explicitly (at
> least in the normal flow of things). It does cause problems of course if
First of all, thanks Tzafrir - I was not aware that the lyx and SI
variants had any bidi chars in them
(I do remember googlin and greppin around before starting to mess with
symbol files - probably did not do that very well - since now I can
easily find the stuff you mention...)
Herouth Maoz wr
At Sun, 31 Oct 2004 07:51:06 +0200,
Herouth Maoz wrote:
>
>
> On Saturday, Oct 30, 2004, at 19:13 Asia/Jerusalem, Amit Aronovitch
> wrote:
>
> > 2) Applications don't always handle them right. For example, OpenOffice
> > handles them correctly, but makes them visible - depending on the font,
>
On Sun, Oct 31, 2004 at 07:51:06AM +0200, Herouth Maoz wrote:
> By the way, the lyx keyboard variant only contains the marking
> characters, not the embedding characters. I had a discussion about this
> in Whatsup this week. I see embedding as more natural, as you don't
> have to think "Hmm, B
On Saturday, Oct 30, 2004, at 19:13 Asia/Jerusalem, Amit Aronovitch
wrote:
2) Applications don't always handle them right. For example, OpenOffice
handles them correctly, but makes them visible - depending on the font,
you usually see an annoying blank square in their place (they should be
invisi
On Sat, Oct 30, 2004 at 07:13:01PM +0200, Amit Aronovitch wrote:
>
> --Boundary_(ID_2y+L2IzElmGKkqvFnkScKQ)
> Content-type: text/plain; charset=ISO-8859-1; format=flowed
> Content-transfer-encoding: 7BIT
>
> Tzafrir Cohen wrote:
>
> >bidi formatting characters.
> >
> >
> >
> Agree that bidi ch
--Boundary_(ID_2y+L2IzElmGKkqvFnkScKQ)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
Tzafrir Cohen wrote:
>bidi formatting characters.
>
>
>
Agree that bidi chars is the way it SHOULD be done, however in current
state of affairs, there's two probl
> www.software.co.il
> +972-8-970-1485(voice)
> +972-54-447-1114(Cell)
>
> - Original Message -
> From: "Micha Feigin" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, October 29, 2004 2:32 AM
> Subject: OO and problems paren
On Fri, Oct 29, 2004 at 02:32:15AM +0200, Micha Feigin wrote:
> I am having problems in open office putting parentheses around english text
> inside hebrew paragraphs when the ending parentheses is at the end of hebrew
> test. Trying to get the following result moves the marked parentheses (read th
CTED]>
Sent: Friday, October 29, 2004 2:32 AM
Subject: OO and problems parentheses in mixed hebrew/english text
> I am having problems in open office putting parentheses around english
text
> inside hebrew paragraphs when the ending parentheses is at the end of
hebrew
> test. Trying to
I am having problems in open office putting parentheses around english text
inside hebrew paragraphs when the ending parentheses is at the end of hebrew
test. Trying to get the following result moves the marked parentheses (read this
right to left, hebrew paragraph):
( )
19 matches
Mail list logo
