1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Grobian wrote: |
5 |
> Danny van Dyk wrote: |
6 |
> |
7 |
>> IMHO a text based file has a big advantage in this proposed application |
8 |
>> over fileformats which use XML: Any administrator can read it with his |
9 |
>> editor of choice, right from the console. |
10 |
> |
11 |
> |
12 |
> This is an important aspect for sure, but why can't such file be |
13 |
> generated from a marked up one? Because the same message will be put in |
14 |
> multiple forms (ideally) it is best to have a version with all the |
15 |
> required meta-data to generate all the other formats, because if you |
16 |
> have to add such meta-data it's usually much worse (= manual or |
17 |
> conditional human work). |
18 |
> |
19 |
> Some people like reading console messages, others plain text mail |
20 |
> messages, others want html marked up mail messages, other others like |
21 |
> reading an rss-feed, and of course there are people that like to read |
22 |
> the full fledged funky marked up with all hyperlinks possible html |
23 |
> version on the web. |
24 |
> I think the only real importance is that all representations can easily |
25 |
> be generated from the original source, be that XML, reStructuredText or |
26 |
> any other format. |
27 |
> |
28 |
> With regard to being it hard to write or not, I think these kind of |
29 |
> messages are very well suited for templates, so it is just a matter of |
30 |
> filling in the message, which should make the underlying format not so |
31 |
> important. |
32 |
> |
33 |
> Just my €0.02 on the XML vs. plain text discussion. |
34 |
> |
35 |
> |
36 |
|
37 |
A very good point. You could even offer a web form for those who don't |
38 |
even want to edit the template by hand. |
39 |
-----BEGIN PGP SIGNATURE----- |
40 |
Version: GnuPG v1.4.1 (GNU/Linux) |
41 |
|
42 |
iD8DBQFDa5YF2QTTR4CNEQARAly+AKCjnT+yONZPAmTO+cccByWeQcaVsQCfQ4Vb |
43 |
K8Cwc/QQNKxAe/Q0VknIOiU= |
44 |
=2Dow |
45 |
-----END PGP SIGNATURE----- |
46 |
-- |
47 |
gentoo-dev@g.o mailing list |