1 |
Thomas Sachau schrieb: |
2 |
> Duncan schrieb: |
3 |
>> Thomas Sachau posted on Sat, 16 Jun 2012 12:31:40 +0200 as excerpted: |
4 |
>> |
5 |
>>> Since i am not that sure about my ability to write formal specs, i am |
6 |
>>> presenting my first draft for further review and suggestions for |
7 |
>>> improvement. |
8 |
>> |
9 |
>> Just a format suggestion. Call it nitpicky if you want, and yes, my |
10 |
>> client isn't perfect, but I'm sure people with a bit of experience |
11 |
>> writing such specs will tell you I'm not alone... |
12 |
>> |
13 |
>> Several of your points ended up as very long single lines. My client can |
14 |
>> wrap, but that wraps the points as well (so for example 2.1 starts in the |
15 |
>> middle of a line). So I was left with the choice to either massively |
16 |
>> horizontally scroll, or of trying to figure out where one point ended and |
17 |
>> another began, since wrapping it... /wrapped/ it, so points appeared in |
18 |
>> the middle of a line. |
19 |
>> |
20 |
>> Please: |
21 |
>> |
22 |
>> * If you use long lines, leave a vertical space (blank line) between |
23 |
>> points so when a client wraps them, they wrap as individual paragraphs. |
24 |
>> |
25 |
>> * Alternatively, wrap at something sensible. (The traditional wrap for |
26 |
>> posting is 72 chars or so, 80 minus a few to allow a few levels of |
27 |
>> quoting without rewrap. I wouldn't complain at 90, but if you're going |
28 |
>> to bother, you might as well go the standard route and avoid further |
29 |
>> issues.) |
30 |
>> |
31 |
>> Long lines as paragraphs would probably be easier especially early in the |
32 |
>> process when you're modifying a lot, but you still risk (even more) |
33 |
>> limited clients having issues with it. YMMV. |
34 |
>> |
35 |
> |
36 |
> I suggest you look for a better client to handle the line wrapping |
37 |
> better. ;-) In the meantime, the same file attached with wrapped lines. |
38 |
> |
39 |
|
40 |
Since there is again no response at all, it seems like everyone is ok |
41 |
with this, so i will propose to add this to the next council agenda for |
42 |
EAPI-5 addition. |
43 |
|
44 |
-- |
45 |
|
46 |
Thomas Sachau |
47 |
Gentoo Linux Developer |