Hi Thibaut,

I tried, using Kile CVS, with a file called:
test

I'm still using 1.6.3, but I'm willing to test a more recent version. Do you plan to release an 1.6.4 version or should I pull the code out of CVS? In the latter case, which branch should I use?

On Tuesday 07 September 2004 13:22, Thibaut Cousin wrote:
> ------- Additional Comments From kde thibaut-cousin net  2004-09-07 13:22
> ------- I'm still using 1.6.3, but I'm willing to test a more recent
> version. Do you plan to release an 1.6.4 version or should I pull the code
> out of CVS? In the latter case, which branch should I use?

There won't be 1.6.4 (unless there is a very critical bug), next version will 
be 1.7. You can checkout CVS without specifying a branch.

thanks,
Jeroen

I've compiled and tried with 1.7b2. It seems to be better, but there is still one string where accented characters are not handled correctly. Here is what I get when I compile a file called "pâte_à_crêpes_salée.tex" with pdflatex:

[PDFLaTeX] pâte_à_crêpes_salée.tex => pâte_à_crêpes_salée.pdf (pdflatex)
pâte_à_crêpes_salée.tex:0:No file p^^c3^^a2te_^^c3^^a0_cr^^c3^^aapes_sal^^c3^^a9e.aux.
[PDFLaTeX] 0 errors, 1 warning, 0 badboxes
[PDFLaTeX] Done!

The file name is correctly displayed by Kile (first line) but the string coming from pdflatex itself is not (second line).

For the record, I'm impressed with that new version. Keep up the good work. :-)

On Tuesday 14 September 2004 08:09, Thibaut Cousin wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=88865
>
>
>
>
> ------- Additional Comments From kde thibaut-cousin net  2004-09-14 08:09
> ------- I've compiled and tried with 1.7b2. It seems to be better, but
> there is still one string where accented characters are not handled
> correctly. Here is what I get when I compile a file called
> "pâte_à_crêpes_salée.tex" with pdflatex:

Delicious ;-)

> [PDFLaTeX] pâte_à_crêpes_salée.tex => pâte_à_crêpes_salée.pdf (pdflatex)
> pâte_à_crêpes_salée.tex:0:No file
> p^^c3^^a2te_^^c3^^a0_cr^^c3^^aapes_sal^^c3^^a9e.aux. [PDFLaTeX] 0 errors, 1
> warning, 0 badboxes
> [PDFLaTeX] Done!
>
> The file name is correctly displayed by Kile (first line) but the string
> coming from pdflatex itself is not (second line).

Here (on RH9, did not test SuSE 9.1 yet) it works ok, the output from pdflatex 
is correct. My LANG variable is set to
en_US.iso885915
however when I set it to
en_US.utf8
then I cannot even open the file. I don't know what is going on, actually.

> For the record, I'm impressed with that new version. Keep up the good work.
> :-)

Thanks!

best,
Jeroen

I think the main point here is that my system is totally configured for Unicode, from the filesystem to the desktop charset. The "official" KDE applications seem OK with that, while Kile has a couple of glitches (nothing too serious, though).

The problem I described above is one of them. There is a second one, which is a bit more annoying, and it looks like it's related.

Let's take a .tex file with accents in its name or in its full name (i.e. with complete path). When I left-click on it in Konqueror, Kile is launched. But the moment Kile tries to open the file, I get an error message. For a file called /home/titi/vidéo/films/films/tex, the error is:

The file file:/home/titi/vid%C3%83%C2%A9o/films/films.tex could not be loaded, as it was not possible to read from it.
Check if you have read access to this file.

But when I open the file from inside Kile with File->Open, it's opened without problem. Maybe Kile doesn't handle correctly the encoding of the string containing the file name from Konqueror?

Can you confirm this bug with kile-1.8?

best,
Jeroen

Using kile-1.8 (Ubuntu package)

-opening file from terminal

$ kile /tmp/é.tex
I got a messagebox with:
"The file file:///tmp/%C3%83%C2%A9.tex could not be loaded, as it was not possible to read from it.
Check if you have read access to this file."

Then title of window is "Document: /tmp/©.tex - Kile"

-opening file from File->open->select /tmp/é.tex
it works, file is opened and window title is correct "Document: /tmp/é.tex - kile"

-opening file from Konqueror (3.5)
go to /tmp
right clic on é.tex
open with... kile
messagebox like one I had when opening from terminal:
"The file file:///tmp/%C3%83%C2%A9.tex could not be loaded, as it was not possible to read from it.
Check if you have read access to this file."

I'm the original submitter of this bugreport. The bug is indeed still there in Kile 1.8.1, exactly as described in comment #8.

My system is now SUSE 10.0 with KDE 3.5, pure Unicode everywhere, and reinstalled from scratch so I don't have any leftover from any old non-Unicode installation.

The bug is triggered when I click on a TeX file in Konqueror to open it in Kile, and it doesn't happen with any other application.

I have the problem described in comment #8 too.

When I call

user@host:/tmp$ kile test_äüö.tex

I get this error:

The file
file:///tmp/test_%C3%83%C2%A4%C3%83%C2%BC%C3%83%C2%B6.tex
could not be loaded, as it was not possible to read from it.

Check if you have read access to this file.

If I enter this address in the Konqueror address bar it is converted to "file:///tmp/test_äüö.tex", which is wrong. Maybe the command line string is encoded twice by Kile somehow. The correct string should be "file:///tmp/test_%c3%a4%c3%bc%c3%b6.tex" which is converted to "/tmp/test_äüö.tex" in Konqueror.

I am using Debian unstable (kile/testing uptodate 1:1.8.1-3.2). My locale is de_DE.UTF-8.

Okay there is now a fix in svn for this.
It works with Suse 10.0 and UTF default.
And this fix will also be part of kile 1.9

Thanks
Thomas Braun

Okay 1.9 is out since a while ago and no comments here.
So I think we got rid of that bug :)

I've run similar tests as the ones in previous comments. I can no longer reproduce the bugs, so things are indeed fine now. :-)

Thank you for your time.