<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Arial'; font-size:12pt; font-weight:400; font-style:normal;">On Wednesday 25 March 2009, Shachar Shemesh wrote:<br>
> Aharon Schkolnik wrote:<br>
> > I have managed to get MS word to work under crossover.<br>
> > I see that if I do :<br>
> ><br>
> ><br>
> > LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword<br>
> ><br>
> ><br>
> > I can insert Hebrew.<br>
><br>
> I'm afraid I'm somewhat to blame for that. I started having Wine<br>
> understand all of the different LC_* environment settings correctly<br>
> (several years ago), but ran out of free time for wine several years ago.<br>
><br>
> I know of two common settings for people who want a Hebrew "enabled"<br>
> machine with an English interface. The one you should officially use is<br>
> to set LANG to he_IL (or he_IL.UTF-8), and to set LC_MESSAGES to en_US.<br>
> This has the effect of setting everything to Hebrew (dates, measurements<br>
> etc.) but the actual language.<br>
><br>
> The second mode (only relevant if you do not work in UTF-8) is to set<br>
> LANG to en_US and LC_CTYPE to he_IL. This means the system is<br>
> essentially speaking English, but with an encoding that has Hebrew support.<br>
><br>
> Despite the fact that the first one is the more correct approach, the<br>
> second one is (or, at least, used to be) the more common one. The<br>
> problem is that not all programs correctly parse all relevant LC_*<br>
> variables, and as a result, not all combinations work as well for all<br>
> programs.<br>
><br>
> Last I checked, Wine only supported the LANG=en_US, LC_CTYPE=he_IL<br>
> combination. In other words, it did not take LC_MESSAGES into account.<br>
><br>
> > Is there a "right" way to set things up so I don't have to set LC_ALL<br>
> > and then run winword ?<br>
><br>
> Not exactly "right", but setting LANG should be "enough".<br>
><br>
> > Ideally, I would just like to choose crossover from the KDE menu, and<br>
> > then choose winword from as the windows command, or even better,<br>
> > create an item on the KDE menu which will just run winword and have it<br>
> > work properly.<br>
><br>
> Use Dotan's solution.<br>
><br>
> Take to heart, however, that Wine also has poor keyboard language<br>
> reporting. The upshot of this is that switching keyboard when typing in<br>
> Word will likely produce reasonable Hebrew *or* reasonable English<br>
> outputs, but not both in the same run. Changing keyboard effectively<br>
> requires changing the LANG variable.<br>
><br>
> Shachar<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I see that mixed Hebrew and English really does NOT work. Very sad ;-(<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
The day is short, and the work is great, | Aharon Schkolnik<br>
and the laborers are lazy, and the reward | <br>
is great, and the Master of the house is | aschkolnik@gmail.com<br>
impatient. - Ethics Of The Fathers Ch. 2 | 054 3344135<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>