Re: Dead keys no longer work

2019-01-12 Thread Daniel CLEMENT
Le samedi 12 janvier 2019 à 11:40 +0100, Pavel Sanda a écrit :
> On Sat, Jan 12, 2019 at 11:08:16AM +0100, Daniel CLEMENT wrote:
> > > So, not specifcally LyX issue... You could try to post bug in
> > > debian
> > > or even with qt...
> > 
> > After some searching, it looks like the bug is already known.
> > 
> > I came across this thread:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=477552
> > 
> > which (following comment #7) lead me to this workaround: I added
> > 
> > export QT_IM_MODULE=xim
> > 
> > to my .xsessionrc file
> 
> Interesting, that shouldn't matter in Qt5. Is it that you still use
> Qt4 in your config?

No, in Debian 9 it's basically Qt5 everywhere (though I do have some
Qt4-related packages installed, e.g. python.qt4)

> My problem is with Qt5.
> 
> > It "works", but frankly, I'd rather not have to do that...
> 
> Agreed, this is just wrong list to ask for the fix, the problem is
> either
> in the config of X/DM or Qt code and it might be difficult to spot
> who is
> actually responsible for the problem...
> Pavel

I do understand that. Yet, I can't help thinking there's something
"special" with the LyX main edit window.

I mean, I have several other Qt apps (Filezilla, Scribus,
Clementine...)--though I don't use them half as much as LyX. None of
them has this problem. Even in LyX, the dead keys do work well within
the dialogs (e.g. file-save as). It's only the main window that shows
the problem.

Moreover, I could check that the dead keys did work properly within LyX
just freshly installed in a live-USB session.

I'm puzzled. As long as my workaround works, all is well... but if it
fails eventually, I'll be in trouble.
-- 
Daniel CLEMENT


Re: Dead keys no longer work

2019-01-12 Thread Pavel Sanda
On Sat, Jan 12, 2019 at 11:08:16AM +0100, Daniel CLEMENT wrote:
> > So, not specifcally LyX issue... You could try to post bug in debian
> > or even with qt...
> 
> After some searching, it looks like the bug is already known.
> 
> I came across this thread:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=477552
> 
> which (following comment #7) lead me to this workaround: I added
> 
> export QT_IM_MODULE=xim
> 
> to my .xsessionrc file

Interesting, that shouldn't matter in Qt5. Is it that you still use Qt4 in your 
config?
My problem is with Qt5.

> It "works", but frankly, I'd rather not have to do that...

Agreed, this is just wrong list to ask for the fix, the problem is either
in the config of X/DM or Qt code and it might be difficult to spot who is
actually responsible for the problem...

Pavel


Re: find the characters U+2029 and U+3B1

2019-01-12 Thread Wolfgang Engelmann



On 12.01.19 09:55, Jürgen Spitzmüller wrote:

Am Freitag, den 11.01.2019, 10:35 +0100 schrieb Wolfgang Engelmann:

I am getting errors in a LyX document which I could trace to
references
in the bibliography. It regards the characters U+2029 (paragraph
end?)
and U+3B1 (ß).

How can I find these in my jabref bib file (or in an editor)?

The most easiest solution is to set an appropriate database encoding in
JabRef's database properties dialog:
http://help.jabref.org/en/DatabaseProperties

The encoding should match the encoding of the LyY document (which is
ISO-8859-15 by default for English and German documents and utf8 if you
use "non-TeX fonts", i.e. XeTeX or LuaTeX).

Jürgen


Yes, Jürgen, that is the best way. I had both (Lyx, Jabref) encodings 
set on utf8, but do not use XeTex or LuaTeX


Wolfgang



Re: find the characters U+2029 and U+3B1

2019-01-12 Thread Jürgen Spitzmüller
Am Freitag, den 11.01.2019, 10:35 +0100 schrieb Wolfgang Engelmann:
> I am getting errors in a LyX document which I could trace to
> references 
> in the bibliography. It regards the characters U+2029 (paragraph
> end?) 
> and U+3B1 (ß).
> 
> How can I find these in my jabref bib file (or in an editor)?

The most easiest solution is to set an appropriate database encoding in
JabRef's database properties dialog:
http://help.jabref.org/en/DatabaseProperties

The encoding should match the encoding of the LyY document (which is
ISO-8859-15 by default for English and German documents and utf8 if you
use "non-TeX fonts", i.e. XeTeX or LuaTeX).

Jürgen


signature.asc
Description: This is a digitally signed message part


Re: find the characters U+2029 and U+3B1

2019-01-12 Thread Wolfgang Engelmann



On 11.01.19 20:14, Wolfgang Engelmann wrote:


On 11.01.19 19:41, Paul A. Rubin wrote:

On 1/11/19 4:35 AM, Wolfgang Engelmann wrote:
I am getting errors in a LyX document which I could trace to 
references in the bibliography. It regards the characters U+2029 
(paragraph end?) and U+3B1 (ß).


How can I find these in my jabref bib file (or in an editor)?

Wolfgang

You did not specify an operating system. On Linux, if you have the 
GNU version of grep installed, one of the answers at 
https://stackoverflow.com/questions/3001177/how-do-i-grep-for-all-non-ascii-characters 
should work. (I like the one that uses :ascii: in the pattern.)


Paul


Thanks, Paul, I use LMint. Will try tomorrow

Wolfgang


This seems to be quite nice, but I haven't tried it yet.

https://pteo.paranoiaworks.mobi/diacriticsremover/

Don't know whether it works also with along bib file. Wolfgang