Nicola Ken Barozzi wrote:
> Andrew C. Oliver wrote:
>
>> Steven Noels wrote:
>>
>>>
>>> *All* instances? Hm. Wouldn't that be troublesome to read? Reminds
>>> me of Wiki webs where people where triggerhappy with hyperreferences.
>>>
>>> A thesaurus of some sorts, easily reachable from each page,
Andrew C. Oliver wrote:
> Steven Noels wrote:
>
>>
>> *All* instances? Hm. Wouldn't that be troublesome to read? Reminds me
>> of Wiki webs where people where triggerhappy with hyperreferences.
>>
>> A thesaurus of some sorts, easily reachable from each page, might
>> perhaps already be enough.
Steven Noels wrote:
> Andrew C. Oliver wrote:
>
>> Here is my first entry :-)
>>
>>
>>
>> Cocoon Syndrome
>>The tendancy whenever anything regarding
>> documentation to focus on a tool for doing the documentation function
>> than actually producing conte
Andrew C. Oliver wrote:
> Here is my first entry :-)
>
>
>
> Cocoon Syndrome
>The tendancy whenever anything regarding documentation
> to focus on a tool for doing the documentation function
> than actually producing content. Generally
> resulting in
Steven Noels wrote:
>
> *All* instances? Hm. Wouldn't that be troublesome to read? Reminds me
> of Wiki webs where people where triggerhappy with hyperreferences.
>
> A thesaurus of some sorts, easily reachable from each page, might
> perhaps already be enough.
>
>
Here is my first entry :-)
Nicola Ken Barozzi wrote:
> Even better, we make a link creating Transformer that transforms all
> instances of " xsp " to a link that links to a cocoon terms dictionary.
>
*All* instances? Hm. Wouldn't that be troublesome to read? Reminds me of
Wiki webs where people where triggerhappy with
At 15:32 12/07/2002 -0500, you wrote:
>Bert Van Kets wrote:
>
>>this is a great idea if implemented properly. I hate being moved to a
>>new page just clicking on a link on an abbreviation.
>>I see different implementations
>>1. a link to a footnote on the same place where the abbreviation is
>>
> From: Bert Van Kets [mailto:[EMAIL PROTECTED]]
>
> At 16:19 12/07/2002 +0200, you wrote:
> >Andrew C. Oliver wrote:
> >>Hi All,
> >>this is mostly a pedantic issue. But one thing that bugs me about
much
> >>of the existing cocoon documentation is the style in which
> >>Cocoon-specific abbrevia
Bert Van Kets wrote:
> this is a great idea if implemented properly. I hate being moved to a
> new page just clicking on a link on an abbreviation.
> I see different implementations
> 1. a link to a footnote on the same place where the abbreviation is
> explained. At least the user would stay
At 16:19 12/07/2002 +0200, you wrote:
>Andrew C. Oliver wrote:
>>Hi All,
>>this is mostly a pedantic issue. But one thing that bugs me about much
>>of the existing cocoon documentation is the style in which
>>Cocoon-specific abbreviations are used. A good example:
>>http://xml.apache.org/cocoon
Andrew C. Oliver wrote:
> Hi All,
>
> this is mostly a pedantic issue. But one thing that bugs me about much
> of the existing cocoon documentation is the style in which
> Cocoon-specific abbreviations are used. A good example:
>
> http://xml.apache.org/cocoon/userdocs/xsp/index.html
>
> The
Having a glossary of terms would be also fine.
We should think about it on Forrest. (I could provide a sample, but it's in
Russian).
Konstantin
> From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]]
>
> Hi All,
>
> this is mostly a pedantic issue. But one thing that bugs me
> about much
> of
Hi All,
this is mostly a pedantic issue. But one thing that bugs me about much
of the existing cocoon documentation is the style in which
Cocoon-specific abbreviations are used. A good example:
http://xml.apache.org/cocoon/userdocs/xsp/index.html
The most basic question is "What does XSP sta
13 matches
Mail list logo
