You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(9) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Patrick W. <pdo...@gm...> - 2009-07-14 19:35:24
|
Hi James IIRC, I used jEdit 4.3 pre 14 (roughly, the latest one available) and the most recent build of Xilize available on their servers. In my most recent updates to the docs, I was relying on Ant to do the document conversion from xil to HTML. I think I'd forgotten the keystrokes that Xilize binds to, and found it a hassle to constantly go to the menu. That's about it. You might ask on the jEdit forums as well. Regards Patrick |
From: Patrick W. <pdo...@gm...> - 2007-07-15 18:19:03
|
Hi Andy Thanks for the very informative write-up! My specific use-case is that I have something that looks like this in my CSS: @page { size: A4; . . . Which uses an enumerated value (from the CSS spec) to specify a page size when laying out in print mode. The property value (A4) is what I need to change (at a minimum; maybe margins as well). I want to generate the HTML (and then PDF) twice, once for A4 output and once for letter output. I think using a property in one of the ways you highlighted would work; in my case, I'd probably use just one or the other from jEdit while writing and checking the output, then generate the two page formats via Ant. Thanks for the docs and the quick turnaround, will try it out in the next few days. Patrick On 7/14/07, Andy Streich <an...@ru...> wrote: > On Saturday 14 July 2007 04:37, Patrick Wright wrote: > > I've written our user's guide using Xilize, and using Flying Saucer, > > can generate PDF from that. FS uses CSS to control all layout and > > formatting, and for PDF output, restricts itself to CSS marked as > > "print" media. > > > > I'd like to have two different versions, one in size A4 and one in US > > Letter. The page size is specified by CSS, which is either embedded or > > linked in. Question is, how could I create two different versions of > > the same doc where only one value (a CSS string) changes? Can I > > somehow pass in variables to replace during generation? > > I took this as an opportunity to extend the Xilize documentation. > > See http://xilize.sourceforge.net/HowTo/index.html > > The section titled "using system properties to control output" might be a > solution for you. Let me know if it's not clear or doesn't help. (I'm not > entirely clear on what you need.) > > Andy > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > xilize-users mailing list > xil...@li... > https://lists.sourceforge.net/lists/listinfo/xilize-users > |
From: Andy S. <an...@ru...> - 2007-07-14 21:09:49
|
On Saturday 14 July 2007 04:37, Patrick Wright wrote: > I've written our user's guide using Xilize, and using Flying Saucer, > can generate PDF from that. FS uses CSS to control all layout and > formatting, and for PDF output, restricts itself to CSS marked as > "print" media. > > I'd like to have two different versions, one in size A4 and one in US > Letter. The page size is specified by CSS, which is either embedded or > linked in. Question is, how could I create two different versions of > the same doc where only one value (a CSS string) changes? Can I > somehow pass in variables to replace during generation? I took this as an opportunity to extend the Xilize documentation. See http://xilize.sourceforge.net/HowTo/index.html The section titled "using system properties to control output" might be a solution for you. Let me know if it's not clear or doesn't help. (I'm not entirely clear on what you need.) Andy |
From: Patrick W. <pdo...@gm...> - 2007-07-14 11:37:38
|
Hi I've written our user's guide using Xilize, and using Flying Saucer, can generate PDF from that. FS uses CSS to control all layout and formatting, and for PDF output, restricts itself to CSS marked as "print" media. I'd like to have two different versions, one in size A4 and one in US Letter. The page size is specified by CSS, which is either embedded or linked in. Question is, how could I create two different versions of the same doc where only one value (a CSS string) changes? Can I somehow pass in variables to replace during generation? Thanks Patrick |
From: Andy S. <an...@ru...> - 2007-07-12 17:56:34
|
Patrick,=20 There is new syntax in Xilize3 for precisely this situation. See below: > Hi, using Xilize 3.0.3 beta. > > I have the following block: > > bcx. > private void run(String[] args) throws Exception { > loadAndCheckArgs(args); > > // Create a JPanel subclass to render the page > XHTMLPanel panel =3D new XHTMLPanel(); > > > which creates the following XHTML > <pre><code>private void run(String[] args) throws Exception { > loadAndCheckArgs(args); > </code></pre> > > <p>// Create a JPanel subclass to render the page<br> > XHTMLPanel panel =3D new XHTMLPanel(); > > The <pre> is ending at the first blank line; I expect it to be broken > by the first block signature (e.g. a p.). This is a problem because > the sample code is about 15 lines long. If I add to the lines it > doesn't break, e.g. Use: bcx. {{ private void run(String[] args) throws Exception { =A0 =A0 loadAndCheckArgs(args); =A0 =A0 // Create a JPanel subclass to render the page =A0 =A0 XHTMLPanel panel =3D new XHTMLPanel(); }} The "{{" and "}}" extend the scope of a signature, any signature except for= =20 "p." You can also use this for nesting: bq. {{ some text in a blockquote pre. some preformated text in the blockquote bq. {{ a blockquote within the blockquote which itself has multiple blocks }} }} Yet another item not obvious in the current documentation. Please keep=20 pointing these things out so I can include them in the next doc update when= I=20 find time to do that. Andy |
From: Patrick W. <pdo...@gm...> - 2007-07-12 16:20:55
|
Hi, using Xilize 3.0.3 beta. I have the following block: bcx. private void run(String[] args) throws Exception { loadAndCheckArgs(args); // Create a JPanel subclass to render the page XHTMLPanel panel = new XHTMLPanel(); which creates the following XHTML <pre><code>private void run(String[] args) throws Exception { loadAndCheckArgs(args); </code></pre> <p>// Create a JPanel subclass to render the page<br> XHTMLPanel panel = new XHTMLPanel(); The <pre> is ending at the first blank line; I expect it to be broken by the first block signature (e.g. a p.). This is a problem because the sample code is about 15 lines long. If I add to the lines it doesn't break, e.g. bcx. private void run(String[] args) throws Exception { loadAndCheckArgs(args); // // Create a JPanel subclass to render the page XHTMLPanel panel = new XHTMLPanel(); TIA Patrick |
From: Andy S. <an...@ru...> - 2007-07-12 16:08:41
|
Patrick, > Ok, it looks like I'm running into a side-effect of natural mode. The > title is defaulting to "NaturalLabel", which is "first line in the > file"--which appears to mean--"first line we parse which has no > signature". I'd love to have a warning about this! I'll see if I can > fix it in my header.xilinc file. The simplist solution may be to turn natural mode off: define. _Natural_ false The easiest way to do this depends on your use of Xilize, however, if you put this line in root.xilconfig at the top of a directory tree it will apply to the whole tree. It can also go in a dir.xilconfig to apply to a subtree. I have updated http://xilize.sourceforge.net/Releases/migrating2-3.html with this tidbit that should have been there from the start. Andy |
From: Patrick W. <pdo...@gm...> - 2007-07-12 10:45:53
|
Ok, it looks like I'm running into a side-effect of natural mode. The title is defaulting to "NaturalLabel", which is "first line in the file"--which appears to mean--"first line we parse which has no signature". I'd love to have a warning about this! I'll see if I can fix it in my header.xilinc file. Thanks Patrick |
From: Patrick W. <pdo...@gm...> - 2007-07-12 10:10:08
|
Bizarre--if I leave the h1 on the first line out, the problem goes away--but the first line is generated as an <h1>. Is there some funky caching going on inside the plugin? Patrick |
From: Patrick W. <pdo...@gm...> - 2007-07-12 10:05:44
|
Hi I have a website and documentation written in XIL and formerly generated into HTML using version 2. I just upgraded to version 3 and I'm getting funny behavior with some of my pages that have headings (h1, h2, etc.). The issue is that Paragraph 1 gets style h1, rather than paragraph (which should be the default. h1. First h1 h2. First h2 Paragraph 1 h2. Second h2 Paragraph 2 partial output <h1>First h1</h1> <h2>First h2</h2> <h1>Paragraph 1</h1> <h2>Second h2</h2> <p>Paragraph 2</p> If I add an explicit p. signature before "Paragraph 1", then "Paragraph 2" is made h1! h1. First h1 h2. First h2 p. Paragraph 1 h2. Second h2 Paragraph 2 <h1>First h1</h1> <h2>First h2</h2> <p>Paragraph 1</p> <h2>Second h2</h2> <h1>Paragraph 2</h1> This is a problem, since I would need to add p. signatured everywhere. I'm hoping there was just some syntax change than I'm missing. Generated with Xilize 3.0.3_31 beta in jEdit. TIA! Patrick |
From: Andy S. <an...@ru...> - 2007-06-04 16:21:41
|
Hi, Xilize can now be installed in jEdit through the normal plugin install=20 procedure. =C2=A0Go to Plugins --> Plugin Manager..., choose the Install ta= b and=20 pick Xilize off the list. Andy |
From: Andy S. <an...@ru...> - 2007-05-15 22:59:55
|
Clarification: you can attempt the relatively big job of modifying the Xilize source OR modify your own code. In the latter case and depending on your needs it might be a very simple task. Andy On Tuesday 15 May 2007 14:57, Andy Streich wrote: > > and I need to get plaing text without Xilize elements (*strong*, **bold** > > etc) > > for full text indexing engine. > > Sorry, Xilize does not provide that ability. You'll have to write a filter > to strip all the inline markup from each block of text -- modify the > source. If you do that and want to supply it as a patch or just as an > example I'd be happy to include it in the next update. This would be nice > functionality to have. > > If you want I'll point you to the part of the code that handles inline > markup -- but it's the most complex and brittle part! I'd like to replace > the piece with a much more sane implementation. > > You might want to consider just stripping out some of the markup like > *strong*, **bold**, and _emphasis_ and replace "link":url with link > (whatever ones are commonly used in the source xil you are processing). > That would be quite simple and not involve touching the Xilize source. > > Andy > > On Tuesday 15 May 2007 12:53, lexius Kh wrote: > > > Hi Evheniy, > > > > > > > Sorry for my English. > > > > I am use Xilize in my web project for post/edit articles. > > > > And I need to clear text from formating element for full text > > > > indexing. Can I do this with xilize-engine.jar? > > > > > > I don't understand your question. With Xilize you have source files > > > (*.xil) and output files (*.html). Do you also need another output > > > > format, > > > > > say, a plain text file (i.e. *.txt) that is stripped of all Xilize > > > markup so you can give that "clean" file to the indexing engine? This > > > not something you can do with Xilize (yet), however, it can probably be > > > done easily by running the *.html output through XSLT. > > > > > > You might consider adding a feature request to the Xilize project so we > > > pick it up in the future. > > > > > > Andy > > > > Thanks for reply. > > I am using xilize in my web project. > > My code: > > > > public class XilizeProcessor implements TextProcessor { > > > > public XilizeProcessor() { > > super(); > > Xilize2.startup(new ReporterStd(), new BeanShell(), new > > HashMap<String, String>()); > > } > > > > public String process(String text) { > > try { > > return (new Xilize2()).xilizeBlocks(text); > > } catch (Exception e) { > > //logger.error(e.getMessage(), e); > > return text; > > } > > } > > > > } > > > > and I need to get plaing text without Xilize elements (*strong*, **bold** > > etc) > > for full text indexing engine. > > > > Evheniy. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > xilize-users mailing list > xil...@li... > https://lists.sourceforge.net/lists/listinfo/xilize-users |
From: Andy S. <an...@ru...> - 2007-05-15 21:57:38
|
> and I need to get plaing text without Xilize elements (*strong*, **bold** > etc) > for full text indexing engine. Sorry, Xilize does not provide that ability. You'll have to write a filter to strip all the inline markup from each block of text -- modify the source. If you do that and want to supply it as a patch or just as an example I'd be happy to include it in the next update. This would be nice functionality to have. If you want I'll point you to the part of the code that handles inline markup -- but it's the most complex and brittle part! I'd like to replace the piece with a much more sane implementation. You might want to consider just stripping out some of the markup like *strong*, **bold**, and _emphasis_ and replace "link":url with link (whatever ones are commonly used in the source xil you are processing). That would be quite simple and not involve touching the Xilize source. Andy On Tuesday 15 May 2007 12:53, lexius Kh wrote: > > Hi Evheniy, > > > > > Sorry for my English. > > > I am use Xilize in my web project for post/edit articles. > > > And I need to clear text from formating element for full text indexing. > > > Can I do this with xilize-engine.jar? > > > > I don't understand your question. With Xilize you have source files > > (*.xil) and output files (*.html). Do you also need another output > > format, > > > say, a plain text file (i.e. *.txt) that is stripped of all Xilize markup > > so you can give that "clean" file to the indexing engine? This not > > something you can do with Xilize (yet), however, it can probably be done > > easily by running the *.html output through XSLT. > > > > You might consider adding a feature request to the Xilize project so we > > pick it up in the future. > > > > Andy > > Thanks for reply. > I am using xilize in my web project. > My code: > > public class XilizeProcessor implements TextProcessor { > > public XilizeProcessor() { > super(); > Xilize2.startup(new ReporterStd(), new BeanShell(), new > HashMap<String, String>()); > } > > public String process(String text) { > try { > return (new Xilize2()).xilizeBlocks(text); > } catch (Exception e) { > //logger.error(e.getMessage(), e); > return text; > } > } > > } > > and I need to get plaing text without Xilize elements (*strong*, **bold** > etc) > for full text indexing engine. > > Evheniy. |
From: lexius K. <lex...@gm...> - 2007-05-15 19:53:36
|
> Hi Evheniy, > > > Sorry for my English. > > I am use Xilize in my web project for post/edit articles. > > And I need to clear text from formating element for full text indexing. > > Can I do this with xilize-engine.jar? > > I don't understand your question. With Xilize you have source files > (*.xil) and output files (*.html). Do you also need another output format, > say, a plain text file (i.e. *.txt) that is stripped of all Xilize markup > so you can give that "clean" file to the indexing engine? This not > something you can do with Xilize (yet), however, it can probably be done > easily by running the *.html output through XSLT. > > You might consider adding a feature request to the Xilize project so we > pick it up in the future. > > Andy Thanks for reply. I am using xilize in my web project. My code: public class XilizeProcessor implements TextProcessor { public XilizeProcessor() { super(); Xilize2.startup(new ReporterStd(), new BeanShell(), new HashMap<String, String>()); } public String process(String text) { try { return (new Xilize2()).xilizeBlocks(text); } catch (Exception e) { //logger.error(e.getMessage(), e); return text; } } } and I need to get plaing text without Xilize elements (*strong*, **bold** etc) for full text indexing engine. Evheniy. |
From: lexius <lex...@gm...> - 2007-05-15 19:37:11
|
On Tuesday 15 May 2007 22:04:07 xil...@li...= =20 wrote: > Hi Evheniy, > > > Sorry for my English. > > I am use Xilize in my web project for post/edit articles. > > And I need to clear text from formating element for full text indexing. > > Can I do this with xilize-engine.jar? > > I don't understand your question. =A0With Xilize you have source files > (*.xil) and output files (*.html). =A0Do you also need another output for= mat, > say, a plain text file (i.e. *.txt) that is stripped of all Xilize markup > so you can give that "clean" file to the indexing engine? =A0This not > something you can do with Xilize (yet), however, it can probably be done > easily by running the *.html output through XSLT. > > You might consider adding a feature request to the Xilize project so we > pick it up in the future. > > Andy Thanks for reply. I am using xilize in my web project. My code: public class XilizeProcessor implements TextProcessor { public XilizeProcessor() { super(); Xilize2.startup(new ReporterStd(), new BeanShell(), new=20 HashMap<String, String>()); } public String process(String text) { try { return (new Xilize2()).xilizeBlocks(text); } catch (Exception e) { //logger.error(e.getMessage(), e); return text; } } } and I need to get plaing text without Xilize elements (*strong*, **bold** e= tc)=20 for full text indexing engine. Evheniy. |
From: lexius K. <lex...@gm...> - 2007-05-15 18:03:55
|
Hi. Sorry for my English. I am use Xilize in my web project for post/edit articles. And I need to clear text from formating element for full text indexing. Can I do this with xilize-engine.jar? Thanks. Evheniy. |
From: Andy S. <an...@ru...> - 2007-05-15 16:12:43
|
Hi Evheniy, > Sorry for my English. > I am use Xilize in my web project for post/edit articles. > And I need to clear text from formating element for full text indexing. > Can I do this with xilize-engine.jar? I don't understand your question. With Xilize you have source files (*.xil) and output files (*.html). Do you also need another output format, say, a plain text file (i.e. *.txt) that is stripped of all Xilize markup so you can give that "clean" file to the indexing engine? This not something you can do with Xilize (yet), however, it can probably be done easily by running the *.html output through XSLT. You might consider adding a feature request to the Xilize project so we pick it up in the future. Andy |
From: lexius <lex...@gm...> - 2007-05-15 12:23:51
|
Hi. Sorry for my English. I am use Xilize in my web project for post/edit articles. And I need to clear text from formating element for full text indexing. Can I do this with xilize-engine.jar? Thanks. Evheniy. |
From: Andy S. <an...@ru...> - 2007-05-07 16:33:50
|
sent new release announcement out on this list two days ago, but it doesn't show in mail list archives this note is just testing the list functionality |
From: Andy S. <an...@ru...> - 2007-05-06 03:58:18
|
Hi, Version 3.0.3 of Xilize has been released (minor changes/bug fixes). Release notes -- http://xilize.sourceforge.net/Releases/rn3.0.3.html Download -- http://sourceforge.net/projects/xilize/ Except for this small effort (which is related to other work I've just begun), I've not been able to do any work on the project these last six months. That's a shame because there have been a steady number of downloads during that time. With that in mind, I hope to announce soon the addition of another developer to the project -- a long time user who has contributed great ideas and excellent testing in the past. Many thanks to the people who have sent me ideas, bug reports, patches, and feature requests. Andy |
From: Andy S. <an...@ru...> - 2006-07-17 05:13:54
|
test2 |