That solves a problem within FlightGear itself, but what about individual aircraft packages? (Which, by the way, is what prompted this thread in the first place.)
As of 2.10, we do have a pretty simple, but integrated, "doc file viewer" (for plain text) that also handles CR/LF for different platforms properly.
It is up to aircraft developers to make use of that feature, or provide docs in another format, such as PDF. We can only really "enforce" best-practices by requiring base package aircraft to follow certain rules.
It would be possible to use the canvas system to render formatted output, i.e. a subset of HTML or even LaTex