Re: lmodern, ae and missing fonts

[Matej Cepl]

On Friday 17 of June 2005 18:01, Martijn Brouwer wrote:
> Which means that lm fonts are fine as long you only use a few
> common font sizes, I assume.

It is OK to use them for whatever -- extrapolation of the sizes 
not covered directly by the fonts is done by lmodern.sty (which 
is what you load with \usepackage{lmodern}) and by browsing 
through the list of files in lmodern package (dpkg -L lmodern on 
Debian) it seems that still you get much more fonts then with 
your average fonts (and possibly still more or at least the same 
number as with Adobe Professional fonts).

Best,

Matej

-- 
Matej Cepl, http://www.ceplovi.cz/matej/blog/
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488
 
He uses statistics as a drunken man uses lamp-posts... for
support, rather than illumination.
  -- Andrew Lang

PStricks figures -> Beamer Presentation

[Rich Shepard]

  I don't have a reference in my saved e-mail messages about this.

  What is the recommended protocol for adding figures drawn with PStricks in
LyX to a beamer presentation, also in LyX? I recall threads about pstricks
not playing nice with pdflatex, so I assume I cannot make a figure float
within the beamer slide and write the pstricks code within that.

Thanks for a pointer,

Rich

--
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
   Voice: 503-667-4517   Fax: 503-667-8863

Re: beamerlyxexample1.lyx

[Paul A. Rubin]

Myriam Abramson wrote:

Hi!

I started to use Beamer. 


I get this error with Beamer 3.05 and LyX 1.3.5 on the example file
beamerlyxexample1.lyx provided with Beamer:

Package xcolor Error: Undefined color `averagebackgroundcolor'.
 ...beamerexample!10!averagebackgroundcolor)}

I do have xcolor installed in the texmf tree and I did a texhash. 


Thanks for any info.


Looks like a bug with Beamer; might be that averagebackgroundcolor was 
defined in earlier versions and leaked through to the recent versions. 
I'll e-mail Till Tantau to let him know.


Meanwhile, as a workaround, you can (in LyX) go to Layout | Document | 
Preamble and replace every instance of averagebackgroundcolor with bg 
(which is the background color in effect for the current slide).  I'm 
not sure it will produce exactly the visual effect Till had in mind, but 
it will at least produce output.  :-)


-- Paul

Re: Words containing Umlaute not found by find and replace

[Georg Baum]

Wolfgang Engelmann wrote:

> would you recommend Westeuropäisch iso 8859-1
>  or Westeuropäisch iso 8859-15?

I guess -15 is best in most cases.

> And what is the difference? (That question should come first...)

-15 has the euro sign, -1 has not (there are other subtle differences that I
forgot, but they are not important for german documents). You can get a
complete list of characters with

man ascii
man iso_8859-1
man iso_8859-15


Georg

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 16:27 schrieb Georg Baum:

Thanks, Georg, I am slowly understanding all that. Each coin has two sides.

> Wolfgang Engelmann wrote:
> > do I understand you right that my Umlaut-problem with the lyx exported
> > .txt and .tex file has nothing to do with lyx, but with the kwrite prg
> > under SuSe (or do I have to set something in kwrite?)
> >  AND
> > with the konqueror (because, if I click on the txt file it also misses
> > the Umlaute?
>
> Yes. There is simply not a general "Text file format" that works for all
> languages.
> The character set autodetection of kwrite does obviously not work so well
> as that of vim or emacs. Everything is fine in kwrite if you change the
> encoding manually: Ansicht->Kodierung festlegen->Westeuropäisch.

would you recommend Westeuropäisch iso 8859-1
 or Westeuropäisch iso 8859-15?
And what is the difference? (That question should come first...)

Wolfgang

Re: Words containing Umlaute not found by find and replace

[Georg Baum]

Wolfgang Engelmann wrote:

> do I understand you right that my Umlaut-problem with the lyx exported
> .txt and .tex file has nothing to do with lyx, but with the kwrite prg
> under SuSe (or do I have to set something in kwrite?)
>  AND
> with the konqueror (because, if I click on the txt file it also misses the
> Umlaute?

Yes. There is simply not a general "Text file format" that works for all
languages.
The character set autodetection of kwrite does obviously not work so well as
that of vim or emacs. Everything is fine in kwrite if you change the
encoding manually: Ansicht->Kodierung festlegen->Westeuropäisch.
Setting the LANG environment variable does not influence kwrite at all.

Concerning your other questions: The reason to switch to UTF8 is to support
more languages in one file: You can't use german umlauts, greek letters and
cyrrillic letters at the same time with the ISO-8xxx character sets, but
you can do so with UTF8, because one character is encoded with two bytes
instead of one -> more available characters.

Since UTF8 has clearly advantages and it will hopefully be supported in the
future by LyX, too, I would rather not change the system default but use
the wrapper script and the ASCIIUTF8 format and converter.
If yoy have filenames with umlauts they will be broken after changing the
system default, so that is another reason not to do it.


Georg

Re: aspell

[Angus Leeming]

Wolfgang Engelmann wrote:
>  how is it with the `personal dictionary´:
>  I tried to put the name of a newly created file
>  `myspellcheckfile.ispell´ (filetype ispell, because that was proposed in
>  Preferences), but that was not accepted. I changed to
>  `myspellcheckfile.aspell´, but that did not work either. So I left it
>  out. And, surprise, it accepts words to be added to a (personal?)
>  spellcheckfile. Where are these words stored and how do I save them?

$ aspell dump config

will output your configuration to stdout.

>  Thanks,
> 
>  Wolfgang
> 
> 
>  ps: I must excuse myself for asking a lot of things which I should find
>  out myself. However, I agreed to talk about Lyx at the soon forthcoming
>  LinuxTag in Karlsruhe, Germany (for `Dante´), and would like to have
>  things working and understand a bit, what I am going to talk about.

Then keep asking ;-)

-- 
Angus

Re: aspell

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 15:57 schrieb Wolfgang Engelmann:
> Am Freitag, 17. Juni 2005 14:55 schrieben Sie:
> > Wolfgang Engelmann wrote:
> > > Spellchecking failed
> > > /usr/lib/aspell/ngerman can not be opened for reading.
> >
> > does it help, if you put "german" in
> > Preferences->Language->Spellchecker->alternative Language?
>

 yes, indeed. How easy. Thanks

>
> > (the aspell dictionary is called german afair, also for "new spellling").

 how is it with the `personal dictionary´:
 I tried to put the name of a newly created file `myspellcheckfile.ispell´
 (filetype ispell, because that was proposed in Preferences), but that was
 not accepted. I changed to `myspellcheckfile.aspell´, but that did not work
 either. So I left it out. And, surprise, it accepts words to be added to a
 (personal?) spellcheckfile. Where are these words stored and how do I save
 them?
 Thanks,

 Wolfgang


 ps: I must excuse myself for asking a lot of things which I should find out
myself. However, I agreed to talk about Lyx at the soon forthcoming
 LinuxTag in Karlsruhe, Germany (for `Dante´), and would like to have things
 working and understand a bit, what I am going to talk about.

-- 
-
Wolfgang Engelmann
Schlossgartenstrasse 22
D-72070 Tübingen

Re: search hits hidden by window

[Martin A. Hansen]

i would like future versions to make sure the text scrolls out of the
way of the window, so this doesnt happen.



martin



On Fri, Jun 17, 2005 at 05:56:23AM -0700, Rich Shepard wrote:
> On Fri, 17 Jun 2005, Martin A. Hansen wrote:
> 
> >when searching or using the spell checker, the "hits" sometimes are hidden
> >behind the search/spell checker window. would it be possible to prevent
> >this?
> 
> martin,
> 
>   Yes. Move that little window out of the way. I have it off the right side
> of the lyx window and shift it around when it blocks something there.
> 
> Rich
> 
> -- 
> Dr. Richard B. Shepard, President
> Applied Ecosystem Services, Inc. (TM)
>    Voice: 503-667-4517   Fax: 503-667-8863

Re: Words containing Umlaute not found by find and replace

[Juergen Spitzmueller]

Wolfgang Engelmann wrote:
> So LANG is used globally, and I can change it locally for certain
> circumstances (eg for lyx)? Could I change it also globally?

You can reset the system encoding to latin-1.
http://portal.suse.com/sdb/de/2004/05/jbartsh_utf-8.html

Jürgen

Re: search hits hidden by window

[Rich Shepard]

On Fri, 17 Jun 2005, Martin A. Hansen wrote:


when searching or using the spell checker, the "hits" sometimes are hidden
behind the search/spell checker window. would it be possible to prevent
this?


martin,

  Yes. Move that little window out of the way. I have it off the right side
of the lyx window and shift it around when it blocks something there.

Rich

--
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
   Voice: 503-667-4517   Fax: 503-667-8863

Re: aspell

[Juergen Spitzmueller]

Wolfgang Engelmann wrote:
> Spellchecking failed
> /usr/lib/aspell/ngerman can not be opened for reading.

does it help, if you put "german" in 
Preferences->Language->Spellchecker->alternative Language?

(the aspell dictionary is called german afair, also for "new spellling").

HTH,
Jürgen

Re: Words containing Umlaute not found by find and replace

[Angus Leeming]

Wolfgang Engelmann wrote:

> Am Freitag, 17. Juni 2005 14:09 schrieb Angus Leeming:
>> Wolfgang Engelmann wrote:
>> >> Now you try and read this exported text file into other, KDE apps.
>> >
>> > kwrite is a KDE apps?
>>
>> Yes. Which means that it is using the Qt libraries, just like LyX.
>>
>> > Is there a reason  they are using UTF-8 encoding?
>>
>> Yes! Your LANG environment variable is set to de_DE.UTF-8.
>> They're just doing what you tell them to do!
> 
> So LANG is used globally, and I can change it locally for certain
> circumstances (eg for lyx)? Could I change it also globally? I would just
> like a decent LANG encoding which takes care of producing my mainly
> german and english documents in the right way. May be I am still
> confused.

Here's how it works:

# Set LANG for lyx only:
$ LANG=de_DE lyx

# Set LANG for this shell.
# Everything spawned by this shell will see this LANG
$ LANG=fr_FR
$ export LANG

# Both lyx and kwrite see LANG=fr_FR.
$ lyx &
$ kwrite &

So, if you want to set LANG glabally, then the place to do it is probably 
/etc/profile, although I'm sure that others will be able to correct me.

>> Wow! I hope you received a telegram from the Queen when you turned 100!
> 
>  Not quite. And unfortunately Germany has not yet a Queen. But this might
> change this fall ;-(

Ahhh well.

Of course, the British already have a German Queen (House of 
Saxe-Coburg-Gotha), so maybe you can share ours ;-)

-- 
Angus

Re: beamerlyxexample1.lyx

[Rich Shepard]

On Thu, 16 Jun 2005, Myriam Abramson wrote:


Package xcolor Error: Undefined color `averagebackgroundcolor'.
...beamerexample!10!averagebackgroundcolor)}


  I, too, found the same error when I tried to view the example file. So, I
gave up on it. Instead, I'm using a different example file (graciously
supplied by a member of our community) and the help I get her (particularly
by Paul).

  There are several insights I've discovered by trial and error because the
specific sequence is not laid out in the manual. For example, placing a list
of eight items in two columns on a slide worked only when the two colums
(under the overall heading of "columns-top-aligned") and grouped and indented
by one level.

  This community here is a tremendous resource and always willing to help.
Try creating the presentation you want (ignoring the example file) and ask
when you get stuck.

Rich

--
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
   Voice: 503-667-4517   Fax: 503-667-8863

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 14:09 schrieb Angus Leeming:
> Wolfgang Engelmann wrote:
> >> Now you try and read this exported text file into other, KDE apps.
> >
> > kwrite is a KDE apps?
>
> Yes. Which means that it is using the Qt libraries, just like LyX.
>
> > Is there a reason  they are using UTF-8 encoding?
>
> Yes! Your LANG environment variable is set to de_DE.UTF-8.
> They're just doing what you tell them to do!

So LANG is used globally, and I can change it locally for certain 
circumstances (eg for lyx)? Could I change it also globally? I would just 
like a decent LANG encoding which takes care of producing my mainly german 
and english documents in the right way. May be I am still confused.
>
> >> > I am slow in those things, sorry, and thanks for your patience.
> >> > Wolfgang
> >>
> >> No worries. I used to have problems understanding this stuff myself.
> >
> > The problem is, that I am probably almost 3 times as old as you are ;-)
>
> Wow! I hope you recieved a telegram from the Queen when you turned 100!

 Not quite. And unfortunately Germany has not yet a Queen. But this might 
change this fall ;-(

Wolfgang

aspell

[Wolfgang Engelmann]

Sorry, its me again

I try to use aspell and get the following info:

Spellchecking failed
/usr/lib/aspell/ngerman can not be opened for reading.

I thought to put a soft link in the texmf directory of my home.
ln -s ngerman /usr/lib/aspell/ngerman
ln: Erzeugen der symbolischen Verknüpfung „/usr/lib/aspell/ngerman“ zu 
„ngerman“: Keine Berechtigung
ok, I should have done it under root. But before I do it, I would like to know 
whether that is the way to do it. 

Is a (virtual) file created in my texmf dir and does texhash take care of it?

Wolfgang

Re: Words containing Umlaute not found by find and replace

[Angus Leeming]

Wolfgang Engelmann wrote:
>> Try
>> export [EMAIL PROTECTED]
>> lyx
>>
>> (or even "LANG=de_DE lyx").
> 
> before I start lyx, and in a shell?

Correct. However, why not rename your lyx executable as "my_lyx" and put a 
little shell script "lyx" in the same directory:

#! /bin/sh
LANG=de_DE my_lyx $*

If you

$ chmod u+x lyx

then you'll be able to use this shell script exactly as if it were your 
lyx binary.


-- 
Angus

Re: Words containing Umlaute not found by find and replace

[Angus Leeming]

Wolfgang Engelmann wrote:
>> Now you try and read this exported text file into other, KDE apps.

> kwrite is a KDE apps?

Yes. Which means that it is using the Qt libraries, just like LyX.

> Is there a reason  they are using UTF-8 encoding?

Yes! Your LANG environment variable is set to de_DE.UTF-8. 
They're just doing what you tell them to do!

> And does it apply to all distributions using KDE? 

Didn't I read Jürgen say that Suse-9.2 uses LANG=UTF-8 by default?

> I do not remember that
> I had these problems in older versions. Did they (the KDE people) switch
> to UTF-8? And again, why? xforms LyX does not have these problems? That
> would explain why I had not seen this before. And a reason, to switch
> back to xforms LyX

The XForms library is like LyX in that it knows nothing about UTF-8 
either.

>> > I am slow in those things, sorry, and thanks for your patience.
>> > Wolfgang
>>
>> No worries. I used to have problems understanding this stuff myself.
> 
> The problem is, that I am probably almost 3 times as old as you are ;-)

Wow! I hope you recieved a telegram from the Queen when you turned 100!

-- 
Angus

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 13:03 schrieb Juergen Spitzmueller:
> Wolfgang Engelmann wrote:
> >  Jürgen,
> >
> > what are your settings in Bearbeiten>Einstellungen>Sprache (sorry, use
> > german)
>
> ngerman. But this is most likely independent (this is the document
> language, not the interface language).
>
> > I do also get no Umlaute and sz in the dropdown menue of Navigating (with
> > the list of chapter names etc): They are spared out by two dashed
> > squares.
> >
> > My is (SuSe9.2, Lyx 1.3.4)
> > \usepackage{babel}
> > \selectlanguage{lang$$}
>
> OK, then it is probably unicode causing problems. SuSE 9.2 uses unicode
> encoding by default, that confuses LyX.
> I'm also using SuSE 9.2, but I have reset encoding to [EMAIL PROTECTED]
>
> > I remember a mail mentioning to use something like
> > LANG=  ...
> > before starting Lyx
> > but can´t find it.
>
> Try
> export [EMAIL PROTECTED]
> lyx
>
> (or even "LANG=de_DE lyx").

before I start lyx, and in a shell?

Thanks,

Wolfgang

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 13:16 schrieb Angus Leeming:
> >  Georg and Angus,
> >
> > do I understand you right that my Umlaut-problem with the lyx exported
> > .txt and .tex file has nothing to do with lyx, but with the kwrite prg
> > under SuSe (or do I have to set something in kwrite?)
> >  AND
> > with the konqueror (because, if I click on the txt file it also misses
> > the Umlaute?
>
> Think about it a little:
>
> LyX can't handle multbyte character encodings internally and so you reset
> your LANG environment variable as seen by it to LANG=de_DE. That way, you
> get LyX menu entries and dialogs that display your umlauts correctly
> because the Qt library that owns these widgets now understands that the
> data it receives from LyX is encoded in latin-1 (ISO-8859-1).
>
> Resetting the LANG environment variable in this way has no effect on the
> data exported by lyx. That's always going to be encoded in latin-1
> (ISO-8859-1).
>
> Now you try and read this exported text file into other, KDE apps. 

kwrite is a KDE apps? Is there a reason  they are using UTF-8 encoding?
And does it apply to all distributions using KDE? I do not remember that I had 
these problems in older versions. Did they (the KDE people) switch to UTF-8? 
And again, why? xforms LyX does not have these problems? That would explain 
why I had not seen this before. And a reason, to switch back to xforms LyX

> Note 
> that the LANG environment variable seen by them is LANG=de_DE.UTF-8. These
> apps aren't 'clever' like vim and emacs; if they see a text file and a
> UTF-8 LANG, then they parse your text file as if it really is encoded in
> UTF-8. So, to make things work in the KDE apps you really must translate
> your text file to UTF-8.

unless I use vi or vim or emacs?

>
> There's no magic there at all, is there?

yes, but seeing a magician performing his tricks does not always mean you know 
what he did.

>
> > I am slow in those things, sorry, and thanks for your patience.
> > Wolfgang
>
> No worries. I used to have problems understanding this stuff myself.

The problem is, that I am probably almost 3 times as old as you are ;-)

Thanks a lot,

Wolfgang

Re: Words containing Umlaute not found by find and replace

[Angus Leeming]

>  Georg and Angus,
> 
> do I understand you right that my Umlaut-problem with the lyx exported
> .txt and .tex file has nothing to do with lyx, but with the kwrite prg
> under SuSe (or do I have to set something in kwrite?)
>  AND
> with the konqueror (because, if I click on the txt file it also misses
> the Umlaute?

Think about it a little:

LyX can't handle multbyte character encodings internally and so you reset 
your LANG environment variable as seen by it to LANG=de_DE. That way, you 
get LyX menu entries and dialogs that display your umlauts correctly 
because the Qt library that owns these widgets now understands that the 
data it receives from LyX is encoded in latin-1 (ISO-8859-1).

Resetting the LANG environment variable in this way has no effect on the 
data exported by lyx. That's always going to be encoded in latin-1 
(ISO-8859-1).

Now you try and read this exported text file into other, KDE apps. Note 
that the LANG environment variable seen by them is LANG=de_DE.UTF-8. These 
apps aren't 'clever' like vim and emacs; if they see a text file and a 
UTF-8 LANG, then they parse your text file as if it really is encoded in 
UTF-8. So, to make things work in the KDE apps you really must translate 
your text file to UTF-8.

There's no magic there at all, is there?

> I am slow in those things, sorry, and thanks for your patience.
> Wolfgang

No worries. I used to have problems understanding this stuff myself.
-- 
Angus

Re: Words containing Umlaute not found by find and replace

[Juergen Spitzmueller]

Wolfgang Engelmann wrote:
>  Jürgen,
>
> what are your settings in Bearbeiten>Einstellungen>Sprache (sorry, use
> german)

ngerman. But this is most likely independent (this is the document language, 
not the interface language).

> I do also get no Umlaute and sz in the dropdown menue of Navigating (with
> the list of chapter names etc): They are spared out by two dashed squares.
>
> My is (SuSe9.2, Lyx 1.3.4)
> \usepackage{babel}
> \selectlanguage{lang$$}

OK, then it is probably unicode causing problems. SuSE 9.2 uses unicode 
encoding by default, that confuses LyX.
I'm also using SuSE 9.2, but I have reset encoding to [EMAIL PROTECTED]

> I remember a mail mentioning to use something like
> LANG=  ...
> before starting Lyx
> but can´t find it.

Try 
export [EMAIL PROTECTED]
lyx

(or even "LANG=de_DE lyx").

HTH,
Jürgen

> Help much appreciated
>
> Wolfgang

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 12:07 schrieb Georg Baum:
> Wolfgang Engelmann wrote:
> > bad news: if I export document as .txt (ASCII), it?s still a problem
> > e.g.:
> > Sie bedankt sich fr alle Anteilnahme an der ?tissinnen-Weihe.
> >  ^^^^
>
> The document is in latin1 encoding. Open it in a decent text editor (such
> as vim :-) ), and it will display it correctly.
>
> > What to do?
>
> If you really need the document in UTF8 encoding do the following after
> export:

I do not care about the encodings as long as they produce the right output for 
my german documents
>
> recode latin1..utf8 file.txt
>
> You could also define your own format ASCIIUTF8 and specify
>
> recode latin1..utf8 < $$i > $$o
>
> as the converter from ASCII to ASCIIUTF8. Then export to ASIIUTF, and you
> never need to convert by hand again.

 Georg and Angus,

do I understand you right that my Umlaut-problem with the lyx exported .txt 
and .tex file has nothing to do with lyx, but with the kwrite prg under SuSe 
(or do I have to set something in kwrite?)
 AND 
with the konqueror (because, if I click on the txt file it also misses the 
Umlaute?

I am slow in those things, sorry, and thanks for your patience.

Wolfgang

Re: Words containing Umlaute not found by find and replace

[Angus Leeming]

Wolfgang Engelmann wrote:
> Do I understand you correctly, that I should use at least under SuSe 9.2
> (and 9.3?) LyX xforms instead of QT? Or switch to another distribution?

Nope. It's sufficient to follow Georg's suggestion of invoking lyx through 
a wrapper script

#! /bin/sh
LANG=de_DE lyx $*

together with his suggestion to define a format ASCIIUTF8 in the 
Edit->Preferences dialog, together with a converter from latin-1 
(ISO-8859-1) to UTF-8.

> Thanks for pointing out the problem. Wolfgang

Perhaps a more general script would take the existing LANG variable and 
strip the '.UTF-8' extension from it:

#!/bin/sh
LANG=`echo $LANG | sed 's/\.UTF-8$//'` lyx $*

-- 
Angus

Re: Words containing Umlaute not found by find and replace

[Angus Leeming]

Wolfgang Engelmann wrote:

> Am Freitag, 17. Juni 2005 11:25 schrieb Georg Baum:
>> Wolfgang Engelmann wrote:
>> > I remember a mail mentioning to use something like
>> > LANG=  ...
>> > before starting Lyx
>> > but can?t find it.
>>
>> That is probably your problem. It should work if you start lyx via
>>
>> LANG=de_DE lyx
>>
>> SuSE 9.2 has LANG=de_DE.UTF-8, and that is not really supported by LyX.
>>
> 
> 
>  Georg
> good news: that did it.
> bad news: if I export document as .txt (ASCII), it´s still a problem
> e.g.:
> Sie bedankt sich fr alle Anteilnahme an der ?tissinnen-Weihe.
>  ^^^^
> What to do?

You mean that your exported .txt document is encoded in ISO-8859-1 whilst 
you'd like it to be encoded in UTF-8?

$ man iconv
$ iconv --from-code ISO-8859-1 --to-code UTF-8 input.txt > output.txt

-- 
Angus

Re: Words containing Umlaute not found by find and replace

[Georg Baum]

Wolfgang Engelmann wrote:

> bad news: if I export document as .txt (ASCII), it?s still a problem
> e.g.:
> Sie bedankt sich fr alle Anteilnahme an der ?tissinnen-Weihe.
>  ^^^^

The document is in latin1 encoding. Open it in a decent text editor (such as
vim :-) ), and it will display it correctly.

> What to do?

If you really need the document in UTF8 encoding do the following after
export:

recode latin1..utf8 file.txt

You could also define your own format ASCIIUTF8 and specify

recode latin1..utf8 < $$i > $$o

as the converter from ASCII to ASCIIUTF8. Then export to ASIIUTF, and you
never need to convert by hand again.


Georg

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 11:43 schrieb Angus Leeming:
> Georg Baum wrote:
> > Wolfgang Engelmann wrote:
> >> I remember a mail mentioning to use something like
> >> LANG=  ...
> >> before starting Lyx
> >> but can?t find it.
> >
> > That is probably your problem. It should work if you start lyx via
> >
> > LANG=de_DE lyx
> >
> > SuSE 9.2 has LANG=de_DE.UTF-8, and that is not really supported by LyX.
>
> Read that as "Not supported at all by LyX".
>
> A brief word of explanation for what is going wrong. Hope it's
> understandable:
>
> What is happening is that the Qt library is using the LANG variable to
> enable it to decipher the char* strings that are passed to it by LyX. LyX
> currently has no multibyte character support at all and so works
> internally with the ISO-8859-1 locale (on a German document). Passing a
> char* string encoded in ISO-8859-1 to a function that things it's
> receiving a string encoded in the entirely different UTF-8 results in the
> weird problems you are seeing in the Search dialog and the menus.
>
> The only thing we have direct control over is the main LyX screen itself.
> Everything else belongs to Qt.

Do I understand you correctly, that I should use at least under SuSe 9.2 (and 
9.3?) LyX xforms instead of QT? Or switch to another distribution?

Thanks for pointing out the problem. Wolfgang

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

Am Freitag, 17. Juni 2005 11:25 schrieb Georg Baum:
> Wolfgang Engelmann wrote:
> > I remember a mail mentioning to use something like
> > LANG=  ...
> > before starting Lyx
> > but can?t find it.
>
> That is probably your problem. It should work if you start lyx via
>
> LANG=de_DE lyx
>
> SuSE 9.2 has LANG=de_DE.UTF-8, and that is not really supported by LyX.
>


 Georg
good news: that did it.
bad news: if I export document as .txt (ASCII), it´s still a problem
e.g.:
Sie bedankt sich fr alle Anteilnahme an der �tissinnen-Weihe.
 ^^^^
What to do?

Wolfgang

Re: Words containing Umlaute not found by find and replace

[Angus Leeming]

Georg Baum wrote:

> Wolfgang Engelmann wrote:
> 
>> I remember a mail mentioning to use something like
>> LANG=  ...
>> before starting Lyx
>> but can?t find it.
> 
> That is probably your problem. It should work if you start lyx via
> 
> LANG=de_DE lyx
> 
> SuSE 9.2 has LANG=de_DE.UTF-8, and that is not really supported by LyX.

Read that as "Not supported at all by LyX". 

A brief word of explanation for what is going wrong. Hope it's 
understandable:

What is happening is that the Qt library is using the LANG variable to 
enable it to decipher the char* strings that are passed to it by LyX. LyX 
currently has no multibyte character support at all and so works 
internally with the ISO-8859-1 locale (on a German document). Passing a 
char* string encoded in ISO-8859-1 to a function that things it's 
receiving a string encoded in the entirely different UTF-8 results in the 
weird problems you are seeing in the Search dialog and the menus.

The only thing we have direct control over is the main LyX screen itself. 
Everything else belongs to Qt.

-- 
Angus

Re: Words containing Umlaute not found by find and replace

[Georg Baum]

Wolfgang Engelmann wrote:

> I remember a mail mentioning to use something like
> LANG=  ...
> before starting Lyx
> but can?t find it.

That is probably your problem. It should work if you start lyx via

LANG=de_DE lyx

SuSE 9.2 has LANG=de_DE.UTF-8, and that is not really supported by LyX.


Georg

Re: Words containing Umlaute not found by find and replace

[Wolfgang Engelmann]

--  Weitergeleitete Nachricht  --

Subject: Re: Words containing Umlaute not found by find and replace
Date: Freitag, 17. Juni 2005 10:59
From: Wolfgang Engelmann <[EMAIL PROTECTED]>
To: Juergen Spitzmueller <[EMAIL PROTECTED]>

sorry Jürgen, forgot to send it to the list

Am Donnerstag, 16. Juni 2005 17:43 schrieben Sie:
> Wolfgang Engelmann wrote:
> > Words containing Umlaute and sz are not found by find and replace
> > (Lyx 1.3.5-1 qt). What do I have to change in the settings?
>
> Works here.

 Jürgen,

what are your settings in Bearbeiten>Einstellungen>Sprache (sorry, use
 german)

I do also get no Umlaute and sz in the dropdown menue of Navigating (with the
list of chapter names etc): They are spared out by two dashed squares.

My is (SuSe9.2, Lyx 1.3.4)
\usepackage{babel}
\selectlanguage{lang$$}

Babel used x
global x
auto begin x
auto ende x
foreign languages marked

I remember a mail mentioning to use something like
LANG=  ...
before starting Lyx
but can´t find it.

Help much appreciated

Wolfgang

---

-- 
-
Wolfgang Engelmann
Schlossgartenstrasse 22
D-72070 Tübingen

Re: Abstract in 3 languages?

[Juergen Spitzmueller]

Jean-Claude Christnach wrote:
> I have to provide an abstract for my resume in 3 different languages. I can
> use the abstract environment several times, but there must be another
> environment in between, but which one does provide only a blank skip? And
> what about the title of the abstract which would be three times
> "Zusammenfassung" but should be "Résumé" the second and "Abstract" the
> third time.

Add to the preamble
\usepackage[ngerman,english,french]{babel}

and switch the language before each abstract in ERT (and Standard 
environment), e.g.
\selectlanguage{ngerman}

Remember to switch back to the document's language after the last abstract.

HTH,
Jürgen

search hits hidden by window

[Martin A. Hansen]

when searching or using the spell checker, the "hits" sometimes are
hidden behind the search/spell checker window. would it be possible to
prevent this?


best regards


martin