| 1 |
Danny van Dyk wrote: |
| 2 |
> IMHO a text based file has a big advantage in this proposed application |
| 3 |
> over fileformats which use XML: Any administrator can read it with his |
| 4 |
> editor of choice, right from the console. |
| 5 |
|
| 6 |
This is an important aspect for sure, but why can't such file be |
| 7 |
generated from a marked up one? Because the same message will be put in |
| 8 |
multiple forms (ideally) it is best to have a version with all the |
| 9 |
required meta-data to generate all the other formats, because if you |
| 10 |
have to add such meta-data it's usually much worse (= manual or |
| 11 |
conditional human work). |
| 12 |
|
| 13 |
Some people like reading console messages, others plain text mail |
| 14 |
messages, others want html marked up mail messages, other others like |
| 15 |
reading an rss-feed, and of course there are people that like to read |
| 16 |
the full fledged funky marked up with all hyperlinks possible html |
| 17 |
version on the web. |
| 18 |
I think the only real importance is that all representations can easily |
| 19 |
be generated from the original source, be that XML, reStructuredText or |
| 20 |
any other format. |
| 21 |
|
| 22 |
With regard to being it hard to write or not, I think these kind of |
| 23 |
messages are very well suited for templates, so it is just a matter of |
| 24 |
filling in the message, which should make the underlying format not so |
| 25 |
important. |
| 26 |
|
| 27 |
Just my €0.02 on the XML vs. plain text discussion. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Fabian Groffen |
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives