[openbeos] Re: Checkins
- From: Michael Phipps <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 03 Mar 2004 20:30:12 -0500
This is an interesting and neat idea.
The general problem is that text translators under R1 really aren't ready for
that, AFAIK. We certainly don't have them for HTML, troff, etc. Even assuming
that we wrote them, there is still an issue in that the translator format for
text doesn't support all of the stuff that one would really need to build
these right. MikeWilber and I have discussed (briefly) some plans for adding
that stuff in R2. I would like to r/w RTF, PDC (Palm Pilot files), HTML,
TROFF, etc. But that would require significant work on the platform as well
as the translators. I don't think that it is likely for R1. :-(
On 2004-03-03 at 20:24:44 [-0500], Mat Hounsell wrote:
> The documentation parts of many open source projects are in various
different
> formats and generate man, info, xhtml, pdf and many other formats.
>
> You will not reach an agreement, as documentation formats are like
programming
> languages and colours every one has a different favourite.
>
> IMOSHO, The BeOS way to handle it will be to use the translators and
provide a
> console and a gui viewer. Apropos could be implemented using a query
interface
> and a context indexation system, like those being discussed on glass
elevator.
>
> It would be useful to augment the translators such that it can generate a
> contents page, a links page and if possible a technical index. The technical
> index could be generated by generating an index and trimming common words
> (/etc/dict).
>
> This would allow a focus on the documentation.
>
> +------+ +------------+ +-------------------------+ +--------+
> | FILE | >> | TRANSLATOR | >> | INDEX, CONTENTS & LINKS | >> | VIEWER |
> +------+ +------------+ +-------------------------+ +--------+
>
>
> Find local movie times and trailers on Yahoo! Movies.
> http://au.movies.yahoo.com
Other related posts:
