Charset encoding and plugins
Submitted by Thursday, 28 April, 2005 - 14:47
on
Hi all,
I'm using jEdit 4.2final with XSLT 0.6.0.
I have to transform some utf-8 .xsl files, but when I click on "Tranform XML" the XSLT plugins says:
===
[error] AWT-EventQueue-0: [Fatal Error] filename.xsl:1:1: Content is not allowed in prolog.
===
because the file starts with the three bytes that identifies utf-8 files.
I don't understand why the File System Browser - that appear when I click on the "Select source XML" or "Add styleshet" buttons on the XSLT GUI - doesn't show the "Encoding >" line in the "Commands" menu...
Obviously I set utf-8 in the Global Options->General->Default Encoding and I disabled the Auto-detection, but XSLT plugin seems to ignore these settings...
Note that the "Encoding >" line in the "Commands" menu of the File System Browser:
appears when I choose File->Open on jedit main menu
doesn't appear when I choose Open file in another plugin (QuickNotepad)
For these reasons I think that the Encoding selection in the File System Browser is disabled when the Browser is invoked
by a plugin, but I don't understand why.
thank you in advance
Andrea
I'm using jEdit 4.2final with XSLT 0.6.0.
I have to transform some utf-8 .xsl files, but when I click on "Tranform XML" the XSLT plugins says:
===
[error] AWT-EventQueue-0: [Fatal Error] filename.xsl:1:1: Content is not allowed in prolog.
===
because the file starts with the three bytes that identifies utf-8 files.
I don't understand why the File System Browser - that appear when I click on the "Select source XML" or "Add styleshet" buttons on the XSLT GUI - doesn't show the "Encoding >" line in the "Commands" menu...
Obviously I set utf-8 in the Global Options->General->Default Encoding and I disabled the Auto-detection, but XSLT plugin seems to ignore these settings...
Note that the "Encoding >" line in the "Commands" menu of the File System Browser:
appears when I choose File->Open on jedit main menu
doesn't appear when I choose Open file in another plugin (QuickNotepad)
For these reasons I think that the Encoding selection in the File System Browser is disabled when the Browser is invoked
by a plugin, but I don't understand why.
thank you in advance
Andrea