Bug 187768

Summary: lilypond-generated textedit urls with accented characters don't work
Product: okular Reporter: Wilbert Berendsen <wbsoft>
Component: generalAssignee: Okular developers <okular-devel>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 0.8.1   
Target Milestone: ---   
Platform: Ubuntu Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Wilbert Berendsen 2009-03-21 08:28:10 UTC
Version:           0.8.1 (using KDE 4.2.1)
OS:                Linux
Installed from:    Ubuntu Packages

I have a LilyPond file called "t√ęst.ly" (i.e. with an accented character in it). When I run LilyPond on it, it generates a PDF with embedded textedit:// urls that point to the source document.

But LilyPond always encodes filenames in textedit:// URLs in UTF-8 encoding.

The problem is that Okular does not know that and so does not find the file and does not call the editor.

Possible solutions:
- don't test for existence of the file, just call the editor and let the editor try to open the file
- perform the conversion from UTF-8 once (using something like QString::fromUtf8(url.toLatin1()))
Comment 1 Pino Toscano 2009-03-21 10:16:48 UTC

*** This bug has been marked as a duplicate of bug 186038 ***