Re: CVS update: /cowiki/misc/development/tests/parser/Basic Formatting/, /cowiki/misc/development/tests/parser/

On 24 Apr 04:28, [email protected] wrote:

> Added:
>    cowiki/misc/development/tests/parser/Basic Formatting/Bold.txt
>    cowiki/misc/development/tests/parser/Basic Formatting/Headings.txt
>    cowiki/misc/development/tests/parser/Basic Formatting/Paragraph.txt
>    cowiki/misc/development/tests/parser/Basic Formatting/Underscore.txt
>    cowiki/misc/development/tests/parser/cowiki-language.html

Is it possible to do three important things:

a) as an unixoid operating system shell is /case sensitive/, to use
   EITHER.UPPERCASE.FOR.FILES.AN.ADMIN.NEEDS or
   UPPERCASE_FILES_THAT_AN_DEVELOPER_NEEDS (ever used a shell and its string
   completition?)

   or

   have less important "files_written_with_lowercase"?

b) avoid spaces in directory and in file names! Escaping spaces with \ is
   the last thing an admin needs while he is working with or setting up
   coWiki. This will also lead to problems on the long run.

   and

c) avoid the strange Windows specific extension suffixes like ".txt"? 
   Nobody needs that (the INSTALL, README, ChangeLog etc., files do not carry
   this), except maybe you have an extra special directory for Windows
   users. In that case this directory should be named as such.

A good exception in the files quoted above is "cowiki-language.html", it
fits a "normal" naming scheme. The others don't. We should get rid of them
and fight the roots.

Is it possible to change it? I of course know, that it is possible, but ask
you if you want to keep the software files keep an order or to want to muddle
it?

regards dtg