[Pmwiki-users] <br> v.s. <br clear> and other issues

[lists@basel-inside.ch]

While implementing pmwiki installations, some of my issues and problems:
(I hope it's not to redundant, I'm new to the group, I haven't read all the
articles yet :-)

EOL:
- to have a special character on the first locical line (also in tables) 
  (like _) to force a <br>
  one reason because [[<<]]
  doesn't break the line (under windows).
  (probably it's not possible to recognise a <eol> correctly and treat it as an
  <eol> in a textarea (as in a text processing programm). 

  \n would be quite intuitiv at least for a programmer :-)

- I never found a character (and a discussion) for *comments*: that 
  would be usefull for a pmwiki beginnner to put some notes.

- I also miss a <cadre> text area ( as in spip) to put code in it, as here:
  http://www.basel-inside.ch/spip/article.php3?id_article=20 
  (it's practical because of ctrl-a) 


DIFF&Patch
  I would allow the option to use diff and patch, because it works also unter
  safe mode if the paths are defined properly in php.ini. and the modules
  are in the paths.
  If diff and patch does nothing (because the commands are missing), it has 
  to be checked wether the result ist ok, otherwise correct errmsg. 
 
  If it's not possible adjust php.ini, it's a help to have 
  php-div and  patch

concatenation wiki.d wiki.. wiklib.d
 Some Features as "WebMenu" and "rename" expect data in wiki.d, I made a 
 changement to the script rename, posted in description of rename. 
 (I have a wikibak.d because in an installation revision doesn't work,
  so I'm looking foreward to php-diff and patch)

Edit Preview (with flexlayout)
 If a GroupHeader is defined, the data show in the textarea and have always 
 be deleted.
 Example: http://www.blug.ch/pm/sys/WikiAdminHint/TestTrail  (edit, preview) 

A extremly strange case (but never mind) 
  http://www.cupconcept.ch/pm/sys/Main/WikiSandbox (publisch works)
  http://www.basel-inside.ch/pm/sys/Main/WikiSandbox  (publish doesn't work!!!)
  (seem's that globals are going lost, but everyting seems 
  correct to me (global settings), and it's the same provider!) 
 -> print *does work* in both cases! 
  If somebody else has this case, let me know. 

Trace:
  Some crucial things should be traceable, like command that potentially 
  don't work. (I have implemented ''TestLog'', but I don't know the 
  critical parts of the scripts).  


Some of these issues may not be new to you, or already fixed. 


regards
Patrick Ogay