On Tue, 31 Mar 2009 13:09:56 +0300
Dotan Cohen wrote:
> > Very different. Math is a complete no go, hebrew and english is a mess,
> > mixed hebrew/english documents and numbers are rarely imported properly,
> > enumerations are messed up completely and changing the document language to
> > hebrew
On Tuesday 31 March 2009, Dotan Cohen wrote:
> > Very different. Math is a complete no go, hebrew and english is a mess,
> > mixed hebrew/english documents and numbers are rarely imported properly,
> > enumerations are messed up completely and changing the document language
> > to hebrew to match t
On Tuesday 31 March 2009, Micha Feigin wrote:
> On Tue, 31 Mar 2009 11:21:42 +0300
>
> Aharon Schkolnik wrote:
> > Thanks for the response.
> > Comments in-line.
> >
> > On Monday 30 March 2009, Dotan Cohen wrote:
> > > > Just to be clear - what I need is a way to edit MS mixed English and
> > > >
Thanks for the reply.
On Tuesday 31 March 2009, Dotan Cohen wrote:
> > Boy, I wish this were true. First, I have found that Open Office has a
> > very difficult time with mixed Hebrew and English. Second, I have found
> > that a mixed Hebrew/English document created with Open Office will get
> > m
> Very different. Math is a complete no go, hebrew and english is a mess,
> mixed hebrew/english documents and numbers are rarely imported properly,
> enumerations are messed up completely and changing the document language to
> hebrew to match the original permutes tab aligned ellements
>
Are you
On Tuesday 31 March 2009, Hetz Ben Hamo wrote:
> Hi,
>
> >> or if you
> >> want, you can use an online solution like Zoho Office which currently
> >> does supports hebrew and english in a mix. I tested that.
> >
> > Interesting, but I don't want to pay.
>
> Pay? for what?? Zoho writer is free for n
> Boy, I wish this were true. First, I have found that Open Office has a very
> difficult time with mixed Hebrew and English. Second, I have found that a
> mixed Hebrew/English document created with Open Office will get messed up
> when viewed with MS Word.
>
> Have others had a different experienc
On Tue, 31 Mar 2009 11:21:42 +0300
Aharon Schkolnik wrote:
> Thanks for the response.
> Comments in-line.
>
> On Monday 30 March 2009, Dotan Cohen wrote:
> > > Just to be clear - what I need is a way to edit MS mixed English and
> > > Hebrew word documents which will be read by Windows users. A
Hi,
>> or if you
>> want, you can use an online solution like Zoho Office which currently
>> does supports hebrew and english in a mix. I tested that.
>
> Interesting, but I don't want to pay.
Pay? for what?? Zoho writer is free for non commercial use.
Zoho writer is free (http://writer.zoho.com
On Monday 30 March 2009, Hetz Ben Hamo wrote:
> Aharon,
>
> If you're using VMWare, I'm not sure about the fact that it doesn't
> support SCSI disks as a raw. After all, SATA disks appear to the
> system as SCSI disks and they are well supported.
From:
http://www.vmware.com/support/reference/lin
Thanks for the response.
Comments in-line.
On Monday 30 March 2009, Dotan Cohen wrote:
> > Just to be clear - what I need is a way to edit MS mixed English and
> > Hebrew word documents which will be read by Windows users. At the monent
> > the only way I can do that is by booting into XP ;-(
>
>
Dotan your right as the Americans say I'll buy that, especially using .pdf.
This type of file covers a multitude of sins and if there's no reason for the
recipient to alter the wording great!
Moshe
--- On Mon, 30/3/09, Dotan Cohen wrote:
From: Dotan Cohen
Subject: Re: Hebrew Under
Aharon,
If you're using VMWare, I'm not sure about the fact that it doesn't
support SCSI disks as a raw. After all, SATA disks appear to the
system as SCSI disks and they are well supported.
You can do another thing: Install VMWare and a minimal XP + Office in
a virtual machine, and then use the
> Just to be clear - what I need is a way to edit MS mixed English and Hebrew
> word documents which will be read by Windows users. At the monent the only
> way I can do that is by booting into XP ;-(
>
If you are creating the documents and others are reading, then there
are two solutions:
1) Ope
On Wednesday 25 March 2009, Hetz Ben Hamo wrote:
> It still has issues. Try to mix hebrew and english in the same line
> and see what I mean.
Yep, I see what you mean !
>
> Hetz
>
> On Wed, Mar 25, 2009 at 10:40 AM, Dotan Cohen wrote:
> >> #!/bin/bash
> >> LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winwo
On Wednesday 25 March 2009, Shachar Shemesh wrote:
> Aharon Schkolnik wrote:
> > I have managed to get MS word to work under crossover.
> > I see that if I do :
> >
> >
> > LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
> >
> >
> > I can insert Hebrew.
>
> I'm afraid I'm somewhat to blame for that. I st
On Wednesday 25 March 2009, Dotan Cohen wrote:
> 2009/3/25 Aharon Schkolnik :
> > I have managed to get MS word to work under crossover.
> > I see that if I do :
> >
> > LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
> >
> > I can insert Hebrew.
> >
> > Is there a "right" way to set things up so I don't
> You need to either use export or put it on the same line as the program you're
> executing. Like:
>
Thanks, that was an untested example. I'm stuck on a Windows
university machine today!
> Please include delimiters to your examples (like ... or <<<...>>>).
>
I'll try to remember that,
On Wednesday 25 March 2009 10:40:25 Dotan Cohen wrote:
> > #!/bin/bash
> > LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
> > wine /path/to/word
>
> Of course, that should have been:
>
> #!/bin/bash
> LC_ALL=he_IL.UTF-8
> $HOME/cxoffice/bin/winword
Since LC_ALL is not defined by default:
{{
sh
It still has issues. Try to mix hebrew and english in the same line
and see what I mean.
Hetz
On Wed, Mar 25, 2009 at 10:40 AM, Dotan Cohen wrote:
>> #!/bin/bash
>> LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
>> wine /path/to/word
>>
>
> Of course, that should have been:
>
> #!/bin/bash
> LC_ALL=h
Aharon Schkolnik wrote:
I have managed to get MS word to work under crossover.
I see that if I do :
LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
I can insert Hebrew.
I'm afraid I'm somewhat to blame for that. I started having Wine
understand all of the different LC_* environment settings corre
> #!/bin/bash
> LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
> wine /path/to/word
>
Of course, that should have been:
#!/bin/bash
LC_ALL=he_IL.UTF-8
$HOME/cxoffice/bin/winword
--
Dotan Cohen
http://what-is-what.com
http://gibberish.co.il
___
Linux-il
2009/3/25 Aharon Schkolnik :
> I have managed to get MS word to work under crossover.
> I see that if I do :
>
> LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
>
> I can insert Hebrew.
>
> Is there a "right" way to set things up so I don't have to set LC_ALL and
> then run winword ?
>
> Ideally, I would
I have managed to get MS word to work under crossover.
I see that if I do :
LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword
I can insert Hebrew.
Is there a "right" way to set things up so I don't have to set LC_ALL and then
run winword ?
Ideally, I would just like to choose crossover from the KDE m
24 matches
Mail list logo
