2afa50bdda
Don't extract TMPL_VAR's as if they were translatable
2004-02-14 07:13:09 +00:00
10bec90dea
Don't complain about </TMPL_IF> or </TMPL_LOOP> being strange attribute
...
syntax; they are fine.
The way TMPL_VAR is warned probably makes more sense now.
2004-02-14 07:07:36 +00:00
0e2ff58b66
This should be still more correct regarding when to warn about TMPL_VAR
...
in attributes
2004-02-14 06:16:36 +00:00
16992ec3f9
More correct version of previous change
2004-02-14 05:50:55 +00:00
93740ec7ba
Make sure that if an attribute contains < or >, a warning is given; these
...
warnings aren't pedantic because (1) if it's a templating directive, it
might expand into something containing a real < and/or >, and (2) if it
contains >, the browser will close the current tag, and (3) if it contains
< and the browser knows what "SGML closed start tags" are (e.g., Mozilla),
the browser will also close the current tag.
2004-02-14 05:46:38 +00:00
a2f07d16f0
Hmm. I didn't know there can be whitespace before and/or after = in
...
attributes...
2004-02-14 05:35:04 +00:00
a10bb7062a
Handle leading or trailing 's as leading or trailing spaces.
...
Make sure they are all trimmed off.
$re_end_entity is now used (by the above); there are  's (no ;)
in our templates.
2004-02-13 03:49:26 +00:00
69589b31f1
Some needed HTML syntax corrections.
2004-02-13 02:46:02 +00:00
b87b492773
The fixed search.marc/search.tmpl (nothing between <textarea></textarea>)
...
caused an eof token to be incorrectly generated by next_token(). This
is now fixed.
2004-02-13 02:42:06 +00:00
5af84e39db
Don't mindlessly spew out 40 lines of text in a warning message if we get
...
too confused. Just say we are too confused.
2004-02-13 01:48:58 +00:00
412847fe93
This way of reporting line numbers should make more sense,
...
esp. for pathetic cases like search.marc/search.tmpl
(missing closing " for an attribute)
2004-02-13 01:27:03 +00:00
1c3cb74b82
Display something useful if the user doesn't specify -f
2004-02-13 01:20:03 +00:00
1f128d7381
Don't issue warnings for unquoted attributes containing [^-\.a-zA-Z0-9]
...
unless --pedantic-warnings is given. These don't seem to cause any trouble,
even in Mozilla's standards compliant mode.
2004-02-13 01:14:18 +00:00
1addd34bb1
Paul's problem #1 is now fixed: Bug in regular expression $re_directive.
...
Put my "grander plan" :-) in the comments
2004-02-13 01:03:18 +00:00
250d1fcefc
Don't extract purely-numeric strings like "1" either
2004-02-13 00:48:52 +00:00
a49634cb34
Seems like I wasn't careful enough recognizing unknown tokens. Incomplete
...
tags like "<b foo" at the end of the file seems to be discarded silently by
Mozilla, even in quirks mode. We now display a warning for these (in case
these ever come up by accident).
2004-02-13 00:42:52 +00:00
bed495ed3e
Minor wording rewrite in warning
2004-02-12 18:25:43 +00:00
906bfbc3d6
Warn about unquoted attribute values containing [^-\.a-zA-Z0-9]
2004-02-12 18:19:17 +00:00
21403fd5cc
extract_attributes now knows what XML-style self-closing tags are
2004-02-12 17:58:24 +00:00
0a9cd4aba1
Warn about <<Prev
2004-02-12 17:44:59 +00:00
33a4d5705a
It now knows what << Prev is, but it may still be confused by other kinds
...
of tag lookalikes
2004-02-12 17:38:42 +00:00
15defe58a9
deleting subs duplicated by error
2004-02-12 13:40:56 +00:00
5affdbf4e7
Handle attributes which are TMPL_VAR's better. It was choking on
...
systempreferences.tmpl.
2004-02-12 09:38:20 +00:00
2f928c4e75
Don't extract strings in hidden values
2004-02-12 09:26:54 +00:00
58951e551f
new feature : stocktaking/inventory.
...
Look in reports menu
(no DB changes)
2004-02-12 09:16:18 +00:00
f247a6c8db
ignoring .tmpl that are hidden files (.somthing.tmpl). hidden files are generated by tools like emacs
2004-02-12 09:13:40 +00:00
0be46ba475
This should be good enough to replace text-extract.pl, but some real
...
testing is needed.
2004-02-12 09:02:39 +00:00
7d244a0b70
This is an experimental filter, based on simple scanning, that *should*
...
(ultimately) work better than the standard filter based on real parsing
of the .tmpl files.
2004-02-12 08:55:14 +00:00
049e6755a8
synch'ing 2.0.0 branch (RC4 tag) and head
2004-02-11 08:57:16 +00:00
af08d677c5
synch'ing 2.0.0 branch (RC4 tag) and head
2004-02-11 08:42:01 +00:00
3635a596cf
synch'ing 2.0.0 branch and head
2004-02-11 08:35:31 +00:00
6f472dbf7b
exit(-1) after usage() is not needed
2004-02-10 09:42:18 +00:00
c8a9c26150
Minor correction in help text
...
This handling for --help works too, and is less wordy
2004-02-10 09:40:21 +00:00
c195908744
Arrays are always defined. We should check its length instead.
2004-02-10 09:36:44 +00:00
8f6651f582
Sync to en template
2004-02-10 08:36:13 +00:00
66d5e2a821
Sync to en, not yet translated
2004-02-10 08:22:24 +00:00
4ceb762e0d
This is more consistent
2004-02-10 08:02:25 +00:00
28db8c0fb0
New file from en
2004-02-10 07:54:36 +00:00
04ec2866ba
SGML syntax correction
2004-02-10 07:54:16 +00:00
4a80f85793
$script_name in template causes runtime error. Should be a TMPL_VAR
2004-02-10 07:38:57 +00:00
39eeb4d233
Sync to new en template
2004-02-10 07:33:35 +00:00
c2e4ee82ce
SGML syntax corrections
2004-02-10 07:07:42 +00:00
b27e60563c
Minor updates
2004-02-10 06:08:35 +00:00
f99540a922
Markup error
2004-02-10 05:58:45 +00:00
4081ed4dc1
New "About" templates from en
...
Minor visual improvements to parameters-{top,bottom}.inc
2004-02-10 05:56:32 +00:00
3a7effdd6e
This makes the fonts look more like the English version
2004-02-10 05:51:58 +00:00
d99d1d53f5
Pedantic SGML syntax correction
2004-02-10 04:59:09 +00:00
4ed4f62165
Spurious attribute in BODY removed
2004-02-10 04:57:27 +00:00
67fcb75630
This wording seems to be more commonly used
2004-02-10 04:46:12 +00:00
5ce1fdc605
Sync to en (new file)
2004-02-10 04:40:56 +00:00
acli
tipaul