Hi, There is an answer from upstream to this bug. Attached below, but you can read/answer it at:
http://bugs.kde.org/show_bug.cgi?id=144749 ----- Forwarded message from Keith Isdale ----- From: Keith Isdale Reply-To: [EMAIL PROTECTED] Date: 13 Jan 2008 06:51:33 -0000 Subject: [Bug 144749] kxsldbg does not honor file encoding ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. http://bugs.kde.org/show_bug.cgi?id=144749 k_isdale tpg com au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED everconfirmed|0 |1 ------- Additional Comments From k_isdale tpg com au 2008-01-13 07:51 ------- Hi, I am the original author of kxsldbg and I recently saw this bug. You wrote: >I'm (not surprisingly) using UTF-8 as encoding for my files, and I'm > also running an UTF-8 locale. But somehow kxsldbg assumes that my files > are in latin1, displaying characters such as german umlaut characters > incorrectly. I assume that the output view is being referred to here which defaults to UTF-8 and this document is not UTF-8 hense the problem. Solution: 1) Click in the "Settings" menu in KXsldbg 2) click "Configure Editor" 3) click "filetype" in the list on left of dialog 4) create a new file type for the ISO-8859-15 encoded document like the following : Name : ISO-8859-15 Document Section : Markup Variables: kate: indent-mode none; encoding ISO-8859-15; File extensions: *.15xml MIME types : text/xml 5) configure kxsldbg to use test1.15.xml as the output file name to use 6) re-run the style sheet then click on the "Output" icon to view the result of the XSLT transformation Do you see what I mean? Regarding the crash mentioned: I still can no reproduce I have used the * xml version 2.6.21 * xslt version 1.1.14 * kxsldbg version that comes with KDE version 3.5.8. Please provide a backtrace/coredump to progress any further and or some general hints on quickly getting a Debian system setup as per this email thread. Regarding the comment that kxsldbg can generate invalid XML; that is correct and is the behavior of the underlying xml/xslt engine used. Sorry not much I can do about that. Try chatting with the people on the libxslt lists since xsltproc generates the same output as kxsldbg in this case. You wrote: > Syntax Highlighting would be nice, too. Syntax highlighting is already done is is provided by Kate if you are not seeing any fancy highlighting then check how you have configured the Kate editor in kxsldbg , see "Configure Editor" mentioned above. You wrote: > > The most useful thing would be to see which template is responsible for > which line of the output file by clicking at the respective nodes > (apart from the line unit being unsuiteable for XML... better set > breakpoints and such on certain nodes!) That is a tough feature to implement and I am yet to port kxsldbg to KDE4. May I suggest that you try the "Walk" functionality in kxsldbg to walk through the stylesheet (select the "Output" view first ) It is possible to set breakpoints on both XSLT nodes and XML nodes; however it is not possible to set breakpoints on the text output functions. You wrote: >P.S. the proper file name for a XSLT file is .xslt IMHO... your default > file name pattern definitely should include .xslt I will see what can be done in the KDE 4 version of kxsldbg to address that problem > And actually you might consider naming it kxsltdbg, since it only does > XSL-T, doesn't it? Sorry I do not plan to change the name of the application at this time. The code to kxsldbg is in SVN so if someone is so motivated that a name change is in order and let me know that they are willing to take up maintenance on this application that would be fine by me -- Keith ----- End forwarded message ----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
