[KBibTeX] Another encoding problem

[Jürgen Spitzmüller]

If I put at the beginning of my bib file (which is encoded in latin9):

@Comment{x-kbibtex-encoding=ISO885915}

open it with KBibTeX3 and click on the source view, the special characters are
not displayed at all. If I switch back, they are displayed in the main list
view as question marks (default import/export encoding is ISO885915 as well).

If I remove the comment from the bib file and open the file with ISO885915 as
default import/export encoding, these problems do not occur. However, the
source preview transforms the special characters to ASCII macros.

This is with latest kbibtex3 svn.

J?rgen

[Thomas Fischer]

Hello J?rgen,

Post by Jürgen Spitzmüller
If I put at the beginning of my bib file (which is encoded in
@Comment{x-kbibtex-encoding=ISO885915}
open it with KBibTeX3 and click on the source view, the special
characters are not displayed at all. If I switch back, they are
displayed in the main list view as question marks (default
import/export encoding is ISO885915 as well).
If I remove the comment from the bib file and open the file with
ISO885915 as default import/export encoding, these problems do not
occur. However, the source preview transforms the special characters
to ASCII macros.

The code which checks for "x-kbibtex-encoding" is case-sensitive.
It should work if you use "@comment" instead of "@Comment".
A fix will be committed to SVN soon.

Bye,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.unix-ag.uni-kl.de/pipermail/kbibtex/attachments/20101019/ef5f80c9/attachment.pgp>

[Jürgen Spitzmüller]

Post by Thomas Fischer
The code which checks for "x-kbibtex-encoding" is case-sensitive.
A fix will be committed to SVN soon.

Thomas,

I'm afraid it doesn't. The issue also occurs with lowercase @comment as well
as with the most recent svn checkout (a console message indicates that the
encoding is switched; I suspect the problem comes from source view -- list
view encoding clashes).

J?rgen

[Thomas Fischer]

Hello J?rgen,

Post by Jürgen Spitzmüller

Post by Thomas Fischer
The code which checks for "x-kbibtex-encoding" is case-sensitive.
A fix will be committed to SVN soon.

Thomas,
as well as with the most recent svn checkout (a console message
indicates that the encoding is switched; I suspect the problem comes
from source view -- list view encoding clashes).

It may be the case that I forgot to upload the changes (just did so).
Please try again. The newest SVN revision is 1000 (nice :-) ).

Bye,
Thomas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.unix-ag.uni-kl.de/pipermail/kbibtex/attachments/20101021/6f09d414/attachment.pgp>

[Jürgen Spitzmüller]

Post by Thomas Fischer
It may be the case that I forgot to upload the changes (just did so).
Please try again. The newest SVN revision is 1000 (nice :-) ).

Same problem with r1000.

J?rgen

[Jürgen Spitzmüller]

Post by Jürgen Spitzmüller

Post by Thomas Fischer
It may be the case that I forgot to upload the changes (just did so).
Please try again. The newest SVN revision is 1000 (nice :-) ).

Same problem with r1000.

Attached is a small example file, so you might try to reproduce the problem:

* open the file. Notice that the encoding seems to be correct.
* switch to source view. Now observe that the umlauts are not displayed.
* switch back to list view and see that the umlauts are now also wrong there.

HTH,
J?rgen

PS. congrats for the dot interview.

[Thomas Fischer]

Hello J?rgen,

Post by Jürgen Spitzmüller

Post by Jürgen Spitzmüller

Post by Thomas Fischer
It may be the case that I forgot to upload the changes (just did
so). Please try again. The newest SVN revision is 1000 (nice :-)
).

Same problem with r1000.

* open the file. Notice that the encoding seems to be correct.
* switch to source view. Now observe that the umlauts are not
displayed. * switch back to list view and see that the umlauts are
now also wrong there.

I tried to reproduce your problem with your example file. With the
changes of revision 1000, switching between list view and source view
works perfectly fine, whereas previous revisions show the bug you are
describing.
Please ensure that you are using the latest SVN version, i.e. no older
libkbibtexpart.so should be installed in your system.

Post by Jürgen Spitzmüller
PS. congrats for the dot interview.

Thanks :-)

Bye,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.unix-ag.uni-kl.de/pipermail/kbibtex/attachments/20101122/291137a6/attachment.pgp>

[Jürgen Spitzmüller]

Post by Thomas Fischer
I tried to reproduce your problem with your example file. With the
changes of revision 1000, switching between list view and source view
works perfectly fine, whereas previous revisions show the bug you are
describing.
Please ensure that you are using the latest SVN version, i.e. no older
libkbibtexpart.so should be installed in your system.

It seems that libkbibtexpart.so was not updated for a while in my tree, so it
kept on reinstalling a version from September.

I ditched my tree now and did a complete new checkout. However, now make
install fails with

/usr/bin/install: cannot stat `.libs/libkbibtexpart.so': No such file or
directory
make[2]: *** [install-kde_moduleLTLIBRARIES] Fehler 1
make[2]: Leaving directory `/home/juergen/updates/kbibtex-svn/src'
make[1]: *** [install-am] Fehler 2
make[1]: Leaving directory `/home/juergen/updates/kbibtex-svn/src'
make: *** [install-recursive] Fehler 1

And indeed, there is no such file.

Any idea?

J?rgen

[Thomas Fischer]

Hello J?rgen,

Post by Jürgen Spitzmüller
It seems that libkbibtexpart.so was not updated for a while in my
tree, so it kept on reinstalling a version from September.
I ditched my tree now and did a complete new checkout. However, now
make install fails with
/usr/bin/install: cannot stat `.libs/libkbibtexpart.so': No such file
or directory
make[2]: *** [install-kde_moduleLTLIBRARIES] Fehler 1
make[2]: Leaving directory `/home/juergen/updates/kbibtex-svn/src'
make[1]: *** [install-am] Fehler 2
make[1]: Leaving directory `/home/juergen/updates/kbibtex-svn/src'
make: *** [install-recursive] Fehler 1
And indeed, there is no such file.
Any idea?

Yes, this is a problem is known to happen with newer autoconf versions
when generating the configure script. If possible, install an older
autoconf, e.g. 2.61.
The svn snapshots tar balls already contain a configure script generated
with such an older autoconf version, so you can directly run the
configure script here.

Bye,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.unix-ag.uni-kl.de/pipermail/kbibtex/attachments/20101122/8ba4bd77/attachment.pgp>

[Jürgen Spitzmüller]

Post by Thomas Fischer
Yes, this is a problem is known to happen with newer autoconf versions
when generating the configure script. If possible, install an older
autoconf, e.g. 2.61.
The svn snapshots tar balls already contain a configure script generated
with such an older autoconf version, so you can directly run the
configure script here.

With the svn snapshots, I face the same problem.

However, I've now installed Cor Blom's openSuse binary of r1000, and can
confirm the problem is resolved!

Thanks,
J?rgen