>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Sure it can. "^[ \t]*([12][0-9][0-9])[ \t]+\"([^ ]+)\"[ \t]+.*"
Wouldn't something like
"^[ \t]*([12][0-9][0-9])[ \t]+\"(.*)\"[ \t]*$"
be better? It avoids junk at the end, does not force a space after the
final ".
Lars> No they were not. At least not in 1.0.4, just look at
Lars> CharacterSet::encodeString in chset.C it returns true if we have
Lars> a str matching one of the strings in the cmap, the number is
Lars> never used.
Yes, I saw that, but I though that it was used elsewhere I did not
see. What is the theory of how this stuff is used, anyway?
Lars> \def{<tex-char>}{nnn}
Lars> could be an alternative
Since nnn almost surely contains braces (\'{e}), this would not be
better. Moreover, this would use a false tex syntax that does not make
sense in TeX. We could want to use the syntax of LaTeX inputenc files,
though, and directly parse that...
Lars> How will that be any nicer? Then lyxlex have one item in its
Lars> keyword table, and you still have to "manually" parse the rest
Lars> of the line.
Except that the 'manually' part does certainly not use more lines of
code than the smart regexp code.
Lars> I really think that to avoid the escaping is nice.
Well, you can have that with LyXLex if you do not quote the second
argument.
