<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-8" http-equiv="Content-Type">
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
<p style="margin-bottom: 0cm; margin-top: 0pt;">Aharon Schkolnik wrote:<br>
</p>
<blockquote cite="mid:200903250955.34437.aschkolnik@gmail.com"
type="cite">
<meta name="qrichtext" content="1">
<style type="text/css">p, li { white-space: pre-wrap; }</style>I have
managed to get MS word to work under crossover.<br>
I see that if I do :<br>
<p style="margin: 0px; text-indent: 0px;"><br>
</p>
LC_ALL=he_IL.UTF-8 ~/cxoffice/bin/winword<br>
<p style="margin: 0px; text-indent: 0px;"><br>
</p>
I can insert Hebrew.<br>
</blockquote>
I'm afraid I'm somewhat to blame for that. I started having Wine
understand all of the different LC_* environment settings correctly
(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"
machine with an English interface. The one you should officially use is
to set LANG to he_IL (or he_IL.UTF-8), and to set LC_MESSAGES to en_US.
This has the effect of setting everything to Hebrew (dates,
measurements etc.) but the actual language.<br>
<br>
The second mode (only relevant if you do not work in UTF-8) is to set
LANG to en_US and LC_CTYPE to he_IL. This means the system is
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
second one is (or, at least, used to be) the more common one. The
problem is that not all programs correctly parse all relevant LC_*
variables, and as a result, not all combinations work as well for all
programs.<br>
<br>
Last I checked, Wine only supported the LANG=en_US, LC_CTYPE=he_IL
combination. In other words, it did not take LC_MESSAGES into account.<br>
<blockquote cite="mid:200903250955.34437.aschkolnik@gmail.com"
type="cite">
<p style="margin: 0px; text-indent: 0px;"><br>
</p>
Is there a "right" way to set things up so I don't have to set LC_ALL
and then run winword ?<br>
</blockquote>
Not exactly "right", but setting LANG should be "enough".<br>
<blockquote cite="mid:200903250955.34437.aschkolnik@gmail.com"
type="cite">
<p style="margin: 0px; text-indent: 0px;"><br>
</p>
Ideally, I would just like to choose crossover from the KDE menu, and
then choose winword from as the windows command, or even better, create
an item on the KDE menu which will just run winword and have it work
properly.<br>
</blockquote>
Use Dotan's solution.<br>
<br>
Take to heart, however, that Wine also has poor keyboard language
reporting. The upshot of this is that switching keyboard when typing in
Word will likely produce reasonable Hebrew *or* reasonable English
outputs, but not both in the same run. Changing keyboard effectively
requires changing the LANG variable.<br>
<br>
Shachar<br>
<br>
<pre class="moz-signature" cols="72">--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
<a class="moz-txt-link-freetext" href="http://www.lingnu.com">http://www.lingnu.com</a>
</pre>
</body>
</html>