Hello Angus,

Monday, November 28, 2005, 2:05:17 PM, you wrote:

> I  suspect  that  this  problem  comes  down  to  a question of what
> encoding  is  seen  by  the GUI toolkit (ru_RU.cp1251 I suppose)
The  locale  is  ru_RU.cp1251,  and the keyboard layouts work via XKB,
which, yes, allows to input in cp1251.

> and  what  encoding  is  used  by  the  LyX document (depends on the
> language settings in the Layout->>Document dialog.)
Of  course,  the  doc  language  is  also  set to Russian (encoding to
cp1251),  and  in  the  encodings file in my ~/.lyx I have also mapped
Russian  to  cp1251, otherwise it wouldn't work (by the way, the value
of  this  file  is not mentioned in the documentation anywhere, and it
should, imho :)

> I  suspect  that we're not very clever at changing the string in one
> 8bit encoding to another 8bit encoding.
>> 1.  Do labels account as popups, and should the above settings have
>> worked in principle? If not, how can I explicitly set the font used
>> for labels?
> You can't. I think that we don't do anything very clever when taking
> the  content  from  the LyX screen and passing it to the GUI library
> that displays the string in a dialog.

So I take it it's a LyX problem, not a toolkit-related one, and LyX is
just  programmed  this  way,  then?

Still, is it possible that the GTK frontend will be without this flaw?

>> 2.  I  noticed  that  xforms  settings  like  "Menu/Popup Font" and
>> "Encoding"  go  into my .lyxrc, which is used by both qt and xforms
>> frontends.  Why  doesn't  lyx-qt  have  the  same font and encoding
>> options as lyx-xforms? is it smarter in any way? Is lyx-qt actually
>> _using_ these additional settings?

> No, it's not.
So it's no problem that all these settings are in my .lyxrc, for both
the frontends. Good.

> These things are used only by the xforms frontend. Qt
> uses the external qconfig tool to control such things in a
                    ^^^^^^^
> consistent way for all Qt apps.
qtconfig, probably?

> I  don't  think it's much consolation, but I think that we've always
> had problems mixing encodings like this.
Well, thanks for the explanation, this problem is a bit annoying, but
it's definitely not enough to put me away from LyX/LaTeX =))

What  really _is_ annoying, is that I have a similar problem with ERT.
This  time,  I  not  only see latin1-garbage in rectangular boxes that
represent ERTs with Russian in it, I also can't see Russian when I try
_inputting_  it  into  the box. It shows again as latin1. So I have to
type blind and hope for the best.

Angus, maybe it's possible to set the font for ERT, again, explicitly?

Or, would it be possible to easily patch LyX so that an encoding of my
choice could be specified and hardcoded into labels and ERTs??

I'm no programmer at all, but if it's a matter of replacing
"some_encoding" with "my_encoding" in some *.h file, I'd giev it a
try, at least for the sake of ERTs.

--
WBR,
Andrei Popov

Using LyX 1.3.6 on Debian GNU/Linux

Reply via email to