You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(9) |
Dec
(2) |
2004 |
Jan
(11) |
Feb
(3) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(9) |
Jun
|
Jul
|
Aug
(4) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Daniel A. <da...@gm...> - 2014-05-17 19:18:31
|
Thanks, that fixed it. Daniel On Sat, 17 May 2014 09:02:55 -0500, Jochen Hoenicke <hoe...@gm...> wrote: > 2014-05-17 7:13 GMT+02:00 Daniel Ajoy <da...@gm...>: >> >> I tried to extend the limits of MAX_PATHNAME_LEN, but that didn't work. >> >> What could be happening? I'm compiling under cygwin. > > Try the attached patch. The response file line length was hard coded > to 128 characters. > > Regards, > Jochen > > --- src/htp.c (Revision 207) > +++ src/htp.c (Arbeitskopie) > @@ -320,7 +320,7 @@ > > BOOL ProcessResponseFile(VARSTORE *parentVarStore, const char *resp) > { > - char textline[128]; > + char textline[MAX_CMDLINE_LEN]; > char defResp[MAX_PATHNAME_LEN]; > char newDirectory[MAX_PATHNAME_LEN]; > char oldDirectory[MAX_PATHNAME_LEN]; |
From: Jochen H. <hoe...@gm...> - 2014-05-17 14:03:02
|
2014-05-17 7:13 GMT+02:00 Daniel Ajoy <da...@gm...>: > > I tried to extend the limits of MAX_PATHNAME_LEN, but that didn't work. > > What could be happening? I'm compiling under cygwin. Try the attached patch. The response file line length was hard coded to 128 characters. Regards, Jochen --- src/htp.c (Revision 207) +++ src/htp.c (Arbeitskopie) @@ -320,7 +320,7 @@ BOOL ProcessResponseFile(VARSTORE *parentVarStore, const char *resp) { - char textline[128]; + char textline[MAX_CMDLINE_LEN]; char defResp[MAX_PATHNAME_LEN]; char newDirectory[MAX_PATHNAME_LEN]; char oldDirectory[MAX_PATHNAME_LEN]; |
From: Daniel A. <da...@gm...> - 2014-05-17 05:14:14
|
I'm getting this error: htp: final output file "./colorear/animal-mamifero-cuadrupedo-herbivoro-con-cuernos.htm" successfully created htp: unable to open "l" as a response file while processing this line: ./colorear/animal-mamifero-cuadrupedo-herbivoro-con-cuernos.htp ./colorear/animal-mamifero-cuadrupedo-herbivoro-con-cuernos.html in htp.rsp I noticed that the string ./colorear/animal-mamifero-cuadrupedo-herbivoro-con-cuernos.htm is 64 characters. I tried to extend the limits of MAX_PATHNAME_LEN, but that didn't work. /* max pathname for UNIX (may be more, but this is sufficient) */ /* (BTW, these values may be incorrect, but they should be sufficient. */ /* Anyone with more concrete values, please email me.) */ #define MAX_PATHNAME_LEN (1024) #define MAX_CMDLINE_LEN (1024) #define MAX_FILENAME_LEN (256) What could be happening? I'm compiling under cygwin. Daniel |
From: Jochen H. <hoe...@gm...> - 2014-04-16 10:43:11
|
A new version of htp, htp-1.18 is now out. The main difference is the support for absolute paths; options now have to start with '-'. The windows binary and linux 32bit binary will be released later. Regards, Jochen 2014-04-15 18:59 GMT+02:00 Daniel Goldman <dgo...@eh...>: > Thanks for making the change. I guess the vote was one to zero in favor > of changing. :) I did my best to double-check. Maybe someone else can > also take a look. > > ////////////////////////// > > In src directory, I looked for '/' or "/" patterns: > > $ grep "'\/'" *.c > $ grep '"\/"' *.c > > def-proc.c: && newHtml.tag[0] == '/' > def-proc.c: else if (newHtml.tag[0] == '/' > htp.c: if((*ptr == '-') || (*ptr == '/')) > htp.c: if((*argv[ctr] == '-') || (*argv[ctr] == '/')) > os.h:#define DIR_DELIMITER '/' > > html.c: if (strcmp(plainPtr, "/") == 0) { > html.c: bufferPtr = stpcpy(bufferPtr,"/"); > os.h:#define OTHER_FILESYSTEM_DELIMITER "/" > os.h:#define OTHER_FILESYSTEM_DELIMITER "/" > os.h:#define DIR_DELIMITER_STRING "/" > > You changed the two lines in htp.c and that seems to be the only changes > needed. The lines in def-proc.c and html.c seem to be about HTML tags. > The lines in os.h seems to be about directory names ending with \ or / > or whatever. So neither needs changing. > > The documentation changes concerning /option vs -option seem OK to me, > based on looking at the online reference. > > I compile under Windows using mingw-w64. I am not an expert on that, it > is confusing for me to compile on windows. > > Thanks again, > Daniel > > On 4/15/2014 4:08 AM, Jochen Hoenicke wrote: >> 2014-04-14 3:33 GMT+02:00 Daniel Goldman <dgo...@eh...>: >>> I would vote for updating the source code to not accept '/' as an option >>> delimiter. In other words, change the program to only allow -option >>> format, and to thus allow absolute paths. >> >> Okay, I updated the htp source code: >> >> http://sourceforge.net/p/htp/code/203 >> >> Can you look over the patch if I missed anything? >> >> I still have to figure out, how building the windows executable worked, >> to make a new release.... >> >> Regards, >> Jochen >> >> ------------------------------------------------------------------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph databases and their >> applications. Written by three acclaimed leaders in the field, >> this first edition is now available. Download your free book today! >> http://p.sf.net/sfu/NeoTech >> _______________________________________________ >> Htp-discuss mailing list >> Htp...@li... >> https://lists.sourceforge.net/lists/listinfo/htp-discuss >> > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/NeoTech > _______________________________________________ > Htp-discuss mailing list > Htp...@li... > https://lists.sourceforge.net/lists/listinfo/htp-discuss |
From: Daniel G. <dgo...@eh...> - 2014-04-15 17:00:07
|
Thanks for making the change. I guess the vote was one to zero in favor of changing. :) I did my best to double-check. Maybe someone else can also take a look. ////////////////////////// In src directory, I looked for '/' or "/" patterns: $ grep "'\/'" *.c $ grep '"\/"' *.c def-proc.c: && newHtml.tag[0] == '/' def-proc.c: else if (newHtml.tag[0] == '/' htp.c: if((*ptr == '-') || (*ptr == '/')) htp.c: if((*argv[ctr] == '-') || (*argv[ctr] == '/')) os.h:#define DIR_DELIMITER '/' html.c: if (strcmp(plainPtr, "/") == 0) { html.c: bufferPtr = stpcpy(bufferPtr,"/"); os.h:#define OTHER_FILESYSTEM_DELIMITER "/" os.h:#define OTHER_FILESYSTEM_DELIMITER "/" os.h:#define DIR_DELIMITER_STRING "/" You changed the two lines in htp.c and that seems to be the only changes needed. The lines in def-proc.c and html.c seem to be about HTML tags. The lines in os.h seems to be about directory names ending with \ or / or whatever. So neither needs changing. The documentation changes concerning /option vs -option seem OK to me, based on looking at the online reference. I compile under Windows using mingw-w64. I am not an expert on that, it is confusing for me to compile on windows. Thanks again, Daniel On 4/15/2014 4:08 AM, Jochen Hoenicke wrote: > 2014-04-14 3:33 GMT+02:00 Daniel Goldman <dgo...@eh...>: >> I would vote for updating the source code to not accept '/' as an option >> delimiter. In other words, change the program to only allow -option >> format, and to thus allow absolute paths. > > Okay, I updated the htp source code: > > http://sourceforge.net/p/htp/code/203 > > Can you look over the patch if I missed anything? > > I still have to figure out, how building the windows executable worked, > to make a new release.... > > Regards, > Jochen > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/NeoTech > _______________________________________________ > Htp-discuss mailing list > Htp...@li... > https://lists.sourceforge.net/lists/listinfo/htp-discuss > |
From: Jochen H. <hoe...@gm...> - 2014-04-15 11:08:21
|
2014-04-14 3:33 GMT+02:00 Daniel Goldman <dgo...@eh...>: > I would vote for updating the source code to not accept '/' as an option > delimiter. In other words, change the program to only allow -option > format, and to thus allow absolute paths. Okay, I updated the htp source code: http://sourceforge.net/p/htp/code/203 Can you look over the patch if I missed anything? I still have to figure out, how building the windows executable worked, to make a new release.... Regards, Jochen |
From: Daniel G. <dgo...@eh...> - 2014-04-14 01:33:15
|
> Using a response file does not work, as it has the same problem. > Updating the source code to not accept '/' as an option delimiter is > easy, just search for '/' in htp.c (with quotes; it occurs twice) and > remove the corresponding branches (from || to the next closing > parenthesis). Options will still be recognized if they are prefixed > with '-'. > > I'm not sure if I should make this the default behaviour under unix. > This may break some existing script. Another possibility would be to > assume that it is a path, if there is no option with that name, or if > there is more than one '/'. This is a bit harder to do and a bit > ugly. > > Regards, > Jochen I would vote for updating the source code to not accept '/' as an option delimiter. In other words, change the program to only allow -option format, and to thus allow absolute paths. Yes, it's best to avoid breaking existing scripts. But how many are really out there that use /option format? And isn't it easy enough to modify existing scripts to switch /option to -option? I would suggest software has to evolve or die. Sometimes old scripts have to be broken if there is a good enough reason. I think the reasons to improve here are good enough. It is a real inconvenience not to allow absolute paths. Can anyone think of another command with this restriction? It seems unusual to have the /option format. I'm familiar with /option format with DOS. But even PowerShell seems to use -option format. Does anyone know why /option format was allowed by original creator of htp? Any advantage to /option format? A final reason for making the change is that it's easy to change. :) I would not be in favor of the possibility to assume it's a path unless same as option name. Sounds complicated and confusing - I don't think /option is worth saving. Anyway, that's my opinion. Whatever is decided, I really like htp and will continue to use. Daniel |
From: Robert H. <bo...@th...> - 2014-04-09 16:06:53
|
On Wednesday, April 9, 2014, Jochen Hoenicke <hoe...@gm...> wrote: > > > >> Produces error message about "unknown option": > >> $ htp /path/temp.x /path/temp2.x > >> > >> Other than not using absolute paths with htp, any suggestions? > > I always used relative paths so I did not notice this problem. > > Using a response file does not work, as it has the same problem. > Updating the source code to not accept '/' as an option delimiter is > easy, just search for '/' in htp.c (with quotes; it occurs twice) and > remove the corresponding branches (from || to the next closing > parenthesis). Options will still be recognized if they are prefixed > with '-'. > > I'm not sure if I should make this the default behaviour under unix. > This may break some existing script. Another possibility would be to > assume that it is a path, if there is no option with that name, or if > there is more than one '/'. This is a bit harder to do and a bit > ugly. > Here's a stupid idea: interpret a double-slash as the start of an absolute pathname. Hence: htp //path/temp.x //path/temp2.x It's clunky, granted, but it shouldn't break any existing behavior and it would grant the ability to use absolute paths with minimal modification at the command-line level. -- Robert Hood - Hixson, TN Web Coder, Steve Jackson Games Next con: TimeGate, May 23-25, 2014 - http://www.timegatecon.org |
From: Jochen H. <hoe...@gm...> - 2014-04-09 10:48:17
|
Hello, > > On Tue, Apr 8, 2014 at 3:47 PM, Daniel Goldman <dgo...@eh...> wrote: >> >> htp 1.16 is version. Apparently because htp allows /option to be a >> command line option, because / can be used to indicate an option, htp >> seems to have a problem with absolute paths on the command line. >> >> Works OK: >> $ htp temp.x temp2.x >> >> Produces error message about "unknown option": >> $ htp /path/temp.x /path/temp2.x >> >> Other than not using absolute paths with htp, any suggestions? I always used relative paths so I did not notice this problem. 2014-04-08 22:24 GMT+02:00 Robert Hood <bo...@th...>: > Maybe you could recompile it removing the slash as an option delimiter. That > way, you could still specify options by using dashes, but you'd avoid that > symbol conflict. > > There's also the option of using a response file instead of manually sending > filenames... Using a response file does not work, as it has the same problem. Updating the source code to not accept '/' as an option delimiter is easy, just search for '/' in htp.c (with quotes; it occurs twice) and remove the corresponding branches (from || to the next closing parenthesis). Options will still be recognized if they are prefixed with '-'. I'm not sure if I should make this the default behaviour under unix. This may break some existing script. Another possibility would be to assume that it is a path, if there is no option with that name, or if there is more than one '/'. This is a bit harder to do and a bit ugly. Regards, Jochen |
From: Robert H. <bo...@th...> - 2014-04-08 20:53:42
|
Maybe you could recompile it removing the slash as an option delimiter. That way, you could still specify options by using dashes, but you'd avoid that symbol conflict. There's also the option of using a response file instead of manually sending filenames... On Tue, Apr 8, 2014 at 3:47 PM, Daniel Goldman <dgo...@eh...> wrote: > htp 1.16 is version. Apparently because htp allows /option to be a > command line option, because / can be used to indicate an option, htp > seems to have a problem with absolute paths on the command line. > > Works OK: > $ htp temp.x temp2.x > > Produces error message about "unknown option": > $ htp /path/temp.x /path/temp2.x > > Other than not using absolute paths with htp, any suggestions? > > Daniel > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Htp-discuss mailing list > Htp...@li... > https://lists.sourceforge.net/lists/listinfo/htp-discuss > -- Robert Hood - Hixson, TN Web Coder, Steve Jackson Games Next con: TimeGate, May 23-25, 2014 - http://www.timegatecon.org |
From: Daniel G. <dgo...@eh...> - 2014-04-08 20:08:06
|
htp 1.16 is version. Apparently because htp allows /option to be a command line option, because / can be used to indicate an option, htp seems to have a problem with absolute paths on the command line. Works OK: $ htp temp.x temp2.x Produces error message about "unknown option": $ htp /path/temp.x /path/temp2.x Other than not using absolute paths with htp, any suggestions? Daniel |
From: Daniel G. <dgo...@eh...> - 2012-12-14 04:36:22
|
Thanks. FWIW (nothing?), it's going OK. For the book, there are sections that get inserted several places. I want to maintain just one copy of repeated sections. I originally defined the sections as CPP macros. That worked, but two problems: 1) No output line breaks, and lines can end up hundreds of columns long, almost awkward to look at. 2) Requires \ line continuation characters in cpp file, another bother to maintain. A few months ago, I moved to putting the sections in a separate file with markers, and using sed / bash to insert them at the proper spot. It worked, and was interesting to set up, but two problems: 1) Slow. Once there were many sections, it took > 5 seconds each time I generated book. I generate it a lot as I make changes. 2) Have to maintain custom code. Today, in a few minutes, I switched to using htp with <block> and <use> to insert the segments. It works perfectly. Basically instantaneous. Daniel Daniel Ajoy wrote: > > On Tue, 04 Dec 2012 16:54:51 -0500, Daniel Goldman <dgo...@eh...> > wrote: > >> Any advice about html pre-processor alternatives? > > htp is the one I keep using. > > Daniel > |
From: Daniel A. <da...@gm...> - 2012-12-04 22:04:14
|
On Tue, 04 Dec 2012 16:54:51 -0500, Daniel Goldman <dgo...@eh...> wrote: > Any advice about html pre-processor alternatives? htp is the one I keep using. Daniel |
From: Daniel G. <dgo...@eh...> - 2012-12-04 21:55:04
|
Any advice about html pre-processor alternatives? I just learned about htp and like it. Seems high quality and well documented. I've already found it useful. Just wondering if other alternative I'm missing. I write C software. I use cpp a lot, and like it. No need for change there. I also maintain web pages and html/pdf documentation. For this text processing, I use cpp/sed/bash a lot. It works, but is cobbled together and inelegant. cpp is not designed for general text processing. cpp is happier with C source code. sed is low level, and not designed as a pre-processor. Recently, I've gotten into book text for conversion to epub/prc/pdf. The cpp/sed combination is getting kind of creaky, and I'm looking for something like htp to add to my toolkit, as I make latex from the book source text. The other html processor I considered was gtml (it's a ubuntu package, like htp). I didn't like 1) syntax overlaps with cpp syntax, 2) written in perl, 3) docs last updated 1999! 4) could not find analog to htp <block> or <inc> tags, so seems kind of weak. I also looked at m4 some, but could not make heads or tails of it. There is also something very complex called Website Meta Language (WML) that includes mph4. Seems pretty powerful, but pretty complex. Anyone know about that? http://www.htmlhelp.com/links/preprocessors.html has links to lots of these things. Anyway, any thoughts about other alternatives for pre-processing html and other general text? Daniel Goldman |
From: Daniel A. <da...@gm...> - 2007-09-01 15:42:31
|
On 31 Aug 2007 at 15:07, Jochen Hoenicke wrote: > > I would appreciate it. > > New version is on sourceforge. I'm a bit out of training with doing > releases, hope I have done it correctly. > The windows version is htp-1.16-Mingw.zip (it uses the mingw gcc-compiler). > it worked thanks. Daniel |
From: Jochen H. <hoe...@gm...> - 2007-08-31 13:07:10
|
Hello, 2007/8/30, Daniel Ajoy <da...@gm...>: > > I can make a new version when I get access to a windows machine again :) > > I would appreciate it. New version is on sourceforge. I'm a bit out of training with doing releases, hope I have done it correctly. The windows version is htp-1.16-Mingw.zip (it uses the mingw gcc-compiler). Regards, Jochen |
From: Daniel A. <da...@gm...> - 2007-08-30 20:34:07
|
> I can make a new version when I get access to a windows machine again :) I would appreciate it. Daniel |
From: Jochen H. <hoe...@gm...> - 2007-08-27 18:44:01
|
Hello Daniel, 2007/8/25, Daniel Ajoy <da...@gm...>: > > <FILE NAME="resources/${file}.pdf" SIZE="kbyte"> > > expands to the letter "f" I think this is a known problem, which is fixed in the CVS. The problem is that the external snprintf library that I used for compiling under windows does not know about floating points. In the CVS I switched to a different snprintf implementation. The problem only occurs under operating systems that do not provide their native snprintf method, e.g. with Win32+ MinGW. I can make a new version when I get access to a windows machine again :) Regards, Jochen |
From: Daniel A. <da...@gm...> - 2007-08-25 17:16:57
|
I'm running this version of HTP: htp 1.15 - HTML pre-processor Copyright (c) 1995-96 Jim Nelson Copyright (c) 2002-03 Jochen Hoenicke under Artistic License [Win32] but this: <FILE NAME="resources/${file}.pdf" SIZE="kbyte"> expands to the letter "f" the log however does not show any error message: [-] resources.htp line 2: dereferencing macro "name" [-] resources.htp line 2: expanding macro "file" to "making_rainbows" My system is a WinXP, with cygwin. Daniel |
From: Daniel A. <da...@gm...> - 2007-05-12 19:31:54
|
if someone wants to compile htp in a freebsd system I had to use gmake and add this to the htp.h file #ifdef __FreeBSD__ typedef unsigned short ushort; typedef unsigned long ulong; #endif Daniel |
From: Jochen H. <hoe...@gm...> - 2007-05-09 08:45:29
|
Hello, 2007/5/8, Rev. Bob <bo...@fe...>: > > Michael M=F6ller <mic...@gm...> wrote: > > > > Results: > > > - Today is Tue May 8 11:33:06 JST 2007. > > > + Today is Tue May 8 11:33:06 JST 2007 > > > + . > > > > Yes, this is not that nice. I guess there is currently no > > possibility to awoid the line break. Probably this is the point > > where we should patch htp. > > That's not always desirable, though. Sometimes you *want* linebreaks like that to be preserved.... Yes, the line break is not from htp, but from the date command. If you want it to be removed, you can use execute=3D"echo -n `date`" or execute=3D"date= | perl -pe chomp" (at least if "echo -n" or perl is supported). I do not think that htp should remove line breaks that external programs produced. Michael answered the other issues accurately, so I do not have to comment o= n them :) Regards, Jochen |
From: Rev. B. <bo...@fe...> - 2007-05-08 19:39:57
|
Michael M=F6ller <mic...@gm...> wrote: > > Results: > > - Today is Tue May 8 11:33:06 JST 2007. > > + Today is Tue May 8 11:33:06 JST 2007 > > + . > > Yes, this is not that nice. I guess there is currently no > possibility to awoid the line break. Probably this is the point > where we should patch htp. That's not always desirable, though. Sometimes you *want* linebreaks like that to be preserved.... -- Robert Hood - Hixson, TN SJG MIB #8595 - Looney Labs Rabbit - Atlas Games Mook |
From: Michael <mic...@gm...> - 2007-05-08 18:24:33
|
Dear Kentaro, On Tuesday 08 May 2007 04:38, Kentaro Fukuchi wrote: > But can I use a block macro in a definition of another macro? > In the original version this was not possible. But when Jochen reworked the way blocks are stored (original: to tmp-files, now: in memory) this limitation was also removed. On Tuesday 08 May 2007 06:48, Kentaro Fukuchi wrote: > Just a small correction: > > <block name="today" expand><file execute="date" redirect></block> > <set message="Today is ${today}."> > <use message> > > Results: > - Today is Tue May 8 11:33:06 JST 2007. > + Today is Tue May 8 11:33:06 JST 2007 > + . Yes, this is not that nice. I guess there is currently no possibility to awoid the line break. Probably this is the point where we should patch htp. Best regards, Michael |
From: Michael <mic...@gm...> - 2007-05-08 18:23:31
|
Dear Kentaro, On Tuesday 08 May 2007 04:38, Kentaro Fukuchi wrote: > But can I use a block macro in a definition of another macro? > In the original version this was not possible. But when Jochen reworked the= =20 way blocks are stored (original: to tmp-files, now: in memory) this=20 limitation was also removed. On Tuesday 08 May 2007 06:48, Kentaro Fukuchi wrote: > Just a small correction: > > <block name=3D"today" expand><file execute=3D"date" redirect></block> > <set message=3D"Today is ${today}."> > <use message> > > Results: > - Today is Tue May 8 11:33:06 JST 2007. > + Today is Tue May 8 11:33:06 JST 2007 > + . Yes, this is not that nice. I guess there is currently no possibility to aw= oid=20 the line break. Probably this is the point where we should patch htp. Best regards, Michael |
From: Kentaro F. <fu...@me...> - 2007-05-08 04:48:42
|
Just a small correction: <block name="today" expand><file execute="date" redirect></block> <set message="Today is ${today}."> <use message> Results: - Today is Tue May 8 11:33:06 JST 2007. + Today is Tue May 8 11:33:06 JST 2007 + . best, Kentaro |