Re: On being web-friendly and why info must die

[Óscar Fuentes]

Paul Eggert <address@hidden> writes:

> That should catch some problems, but it's not enough.  Typically I
> focus on that editing the .texi file first to get the content right.
> Then, I want to make sure the result is readable so I generate the
> output and look at it.

I reckon that those issues are related to the texinfo format,
specifically. Other formats can be checked for readability without
exporting them first.

> Problems with looks often include
> fairly-mundane things like a capitalized word at sentence end which
> messes up later spacing, things which one can easily see when looking
> at the info output, but which one can't easily expect a text editor to
> catch.

Isn't it possible to defer those issues to an advanced stage where the
areas with documentation changes are checked ``en-masse'' instead of
checking one change at a time?