Re: accented letters....

[email protected] Fri, 4 Jun 2004 21:02:37 +0200
Newsgroups gmane.comp.tex.texinfo.pretest
Message-ID <[email protected]>
It's readable enough thanks to syntax highlighting. I examined many markup languages and texinfo dialect is one of the most easily readable and understandable, directly in source, particularly when different command words have different colours.

Moreover, it is enough to shortern command works (example @b = @strong), to render it even more readable.

Also this may be done with a preprocessor, as I do. This because when using @alias command, makeinfo makes a good html output, tex not always interprets correctly aliases. So a "sed"-like preprocessing is sufficient to transform a shortened markup code into the standard texinfo code.

Cheers,


Valentino
[email protected]

On Fri, 04 Jun 2004 14:48:01 +0200
"Eli Zaretskii" <[email protected]> wrote:

> > From: Karl Eichwalder <[email protected]>
> > Date: Thu, 03 Jun 2004 08:23:43 +0200
> > 
> > "Eli Zaretskii" <[email protected]> writes:
> > 
> > > We could have a special feature in the Emacs Texinfo mode to ease the
> > > pains of that: Emacs can insert @'a when you type the corrsponding
> > > Latin-1 character.
> > 
> > I guess it is not the goal to make the source file unreadable ;)
> 
> I don't see how that makes Texinfo any more unreadable than it already
> is, what with all those @code, @acronym, etc.
> 
> In any case, how should Texinfo support non-ASCII characters is
> something as yet to be discussed and determined.  No one said that
> doing that in literal UTF-8 is the one truly way.
> 
> > I recommend to go for 'recode' as a preprocessor:
> 
> I think the issue at hand is how should Texinfo look _after_ it's
> preprocessed, not what machinery do we use to produce it.
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
[email protected]
http://ff0.org/mailman/listinfo/texinfo-pretest