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

[Eli Zaretskii]

> From: Óscar Fuentes <address@hidden>
> Date: Wed, 10 Dec 2014 20:47:21 +0100
> 
> > 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?

If you push unchecked changes, and they cause errors, you might
confuse people or even break the build.  So I always generate the docs
before committing any documentation changes, even the smallest ones.