Thanks for fixing this. I have looked at the python script that
substitutes LaTeX commands. pdfTeX and MiKTeX are not mentioned in
TeX-on-Debian.sgml and Debian-TeX-Policy.sgml so they could be removed
from texify-tex-output unless this script will be used for other
documents.
Regards,
Miguel
--- texify-tex-output
+++ texify-tex-output.new
@@ -66,12 +66,10 @@
# of a chunk; instead, we *search* (using regexp.search()) for the first match
# of that regexp in the chunk.
body_substitutions = [(r"\bTeX\b", r"\\TeX{}"),
- (r"\bpdfTeX\b", r"pdf\\TeX{}"),
(r"\bMetafont\b", r"\\MF{}"),
(r"\bLaTeX\b", r"\\LaTeX{}"),
(r"\bConTeXt\b", r"Con\\TeX{}t"),
- (r"\bteTeX\b", r"te\\TeX{}"),
- (r"\bMiKTeX\b", r"MiK\\TeX{}")]
+ (r"\bteTeX\b", r"te\\TeX{}")]
# List of (command_name, number_of_args) tuples for LaTeX commands which
# should not be subject to the regexp substitution (neither the command name,
On Tue, Mar 13, 2007 at 08:55:49AM +0100, Florent Rougon wrote:
> Frank Küster <[EMAIL PROTECTED]> wrote:
>
> > I agree. Except that I think that we can assume that a "TeXstring" with
> > a hyphen after it can also be replaced always:
> >
> > (^|[[:space:]])TeX(-|[[:space:]]|$)
> >
> > at least until we find that it causes an error (a hyphen in front *and*
> > after TeX gives a false positive, the filename Debian-TeX-Policy).
>
> This would probably be OK in most cases, yes. OTOH, I don't see many
> "English" words such as TeX-related that would benefit from such a
> treatment. So, this would mostly apply to words like TeX-XeT, which
> would probably benefit from a special case anyway (replacing them with
> their own command).
>
> BTW: I forgot to write it in my previous mail, but the regexes I
> proposed are valid with sed *provided* we use its -r option (aka
> --regexp-extended).
>
> Regards,
>
> --
> Florent
