Xilize 2.0.3 release notes

build 33 May 1, 2006

files in this package

Note: since this package was first distributed hosting has moved to SourceForge.

file size notes
xilize-jar_2.0.3_33.tar 200-KB un-tar to get Xilize.jar and copy to jEdit jars directory (see jEdit's Utilities > Settings Directory > jars). See here to use the jEdit plugin and here to execute from the command line.
xilize-source_2.0.3_33.tar.gz 119-KB source code and build files to generate Xilize.jar
xilize-docs_2.0.3_33.tar.gz 1.2-MB Xilize2 website source. All source files — *.xil, *.xilinc, *.js, *.css, *.jpg, etc. — for building the Xilize web pages (those on the old centeredwork.com site); a complete example of using Xilize2 for a sophisticated task. See this section of the User Guide for an explanation of the files. To build locally, unzip the zip file, open one of the *.xil files in jEdit, and press the project key in XAA.

The User Guide contains some notes on install and setup here

minimum requirements

2.0.3 changes

mode file updated

The change is related to syntax-highlighting of table-row markup.

Update your mode file: After you have updated Xilize.jar, go to Plugins > Xilize > options and press the install Xilize mode button. The new mode file (stored in the jar) will overwrite your current one.

bug fix: floating images markup broken

!> imageUrl! was translating as !> imageUrl! correct translation is <img src="imageUrl" style="float:right;" />

defect introduced in build 31, fixed in 33

bug fix: link markup improved

Markup of the form "text" text "linkText":url was translating as <a href="url">text" text "linkText</a> instead of "text" text <a href="url">linkText</a>. Problem occurred when link markup followed a regular quotation in the same block of text.

defect (probably) introduced in build 31, fixed in 33

new define key

Added _OSinfo_ key which is set to the value of relevant Java system properties (os.name, os.version, and os.arch).

documentation changes

Added a "special blocks" section to the quick reference. Both HTML-comment and no-translation block markup had been omitted in error.

2.0.2 changes

added link-to-image markup.

General syntax: !imageURL!:linkURL

!images/xilbox.png!:http://www.centeredwork.com/xilize2

translates to

<a href="http://www.centeredwork.com/xilize2"><img src="images/xilbox.png" /></a>

The old syntax — "!imageURL!":linkURL — still works but is more typing.

headAppend is now an alias for headElementAdd special key

It wins on two counts: more descriptive and shorter. Of course it is an additive define just like headElementAdd now is — a true alias.

headElementAdd is deprecated (which likely means it will go away sometime in 2007 :-).

bug fix: span-caps in link title text

"Xilize2 (markup engine to generate HTML from plain text)":index.html was generating a <span class="caps"> element in the title text of the <a> element when it found a acronym-like word. (This is correct behavior when the the text is not part of title or alt attributes.)

StringBuffer changed to StringBuilder

...as part of the Java5 upgrade. Note: StringBuffer is synchronized, StringBuilder is not. There may be some small performance gain on older systems.

new customProlog and customEpilog keys

Here is the new part of the docs:

key value default description
prolog true | false true adds <!DOCTYPE>, <html>, and <head> elements and the <body> start tag to the beginning of the HTML file. The content of the <head> element is determined by the customization settings above.
epilog true | false true adds </body></html> to end of input.
customProlog text adds text to the top of the generated HTML file irrespective of the prolog setting. Note: all head element customization settings will be ignored. Thus, define. style and define. script will have no effect.
customEpilog text adds text to the bottom of the generated HTML file irrespective of the epilog setting.

Only when writing that new part did I realize the consequences of implementing a custom prolog this way. Mostly I'm wondering how functional it is for users. Personally, I don't see the use case given the consequence of not being able to use define. style and define. script. As always, feedback appreciated.

2.0.1 changes

Java 1.5 required

Java 1.5 (a.k.a. Java5) is now required. Minimum Java was incorrectly specified as 1.4.

new special keys for external CSS

Documentation update here.

Added special keys cssPreferred and cssAlternate for generation of <link> elements for external CSS. The complete set of special keys for external CSS is now:

key stylesheet type example of generated <link> element
css persistent <link href="file1.css" rel="stylesheet" type="text/css" />
cssPreferred preferred <link href="file2.css" title="title2" rel="stylesheet" type="text/css" />
cssAlternate alternate <link href="file3.css" title="title3" rel="alternate stylesheet" type="text/css" />

Syntax allows for multiple files of each type which will generate multiple <link> elements of that type:

define. css fileA.css fileB.css fileC.css

or

define. css
fileA.css
fileB.css
fileC.css

Preferred and alternate stylesheets require a title:

define. cssPreferred
titleE fileE.css

define. cssAlternate
titleL fileL.css
titleM fileM.css
titleN fileN.css

or if you have just one:

define. cssPreferred titleE fileE.css

define. cssAlternate titleL fileL.css

multiple class names in modifiers allowed

Previously just a single class name could be given in a modifier string. For example:

 h2(special). heading text

Now multiple class names may be given:

h2(special,red,notable). heading text

Class names used in this way must be separted by commas (,) with no surrounding whitespace.

special key headElementAdd is now additive

Special key headElementAdd is now additive; that is, if defined multiple times its values will be aggregated.