Follow-up Comment #13, task #2874 (project savane): > I still don't like the idea very much to add some special tags to every DB > entry. I think it would be a cleaner solution to disable the wiki markup for > those entries completely, even for future entries. We could then allow the > markup only for project descriptions and recipes.
No no, in many cases, in comments and elsewhere, it would be truly nice to be able to do some formatting stuff. Indeed, the wiki have to handle 2 levels of formatting: for recipes content, news contents, project description ; for comments and usual items details. In the first level, headers and hr should be allowed, not in the second level. If we don't go on special tags for every db entry (I admit you are right, it is not an uber-clean way to do things), at least we should double markup signs, **strong**, //em//, __underline__. And in this case, yes I guess we should provide an update script that would use the wiki formatting regexp to detect whether it would do any conversions in previous items. And if it does, it should ask whether a #verbatim# tag should be added around the incriminated words (not the whole item details or comment) so the admin when upgrading his installation would be 100% sure that after the upgrade there are no uncatched issue, no bits of code altered. (asking him to do everything by hand in phpmyadmin is a no go even if only 1% of the items are affected. On LCG Savannah, it would mean editing more than 130 items! On another topic, I've just realized I'm a bit annoyed by the underline idea and the /complexity/. Normally, in a word where you study litteracy, you are supposed to use underline to mean italic when you are writing by hand. Underline is supposed to be only a clone of italic more doable for a human. You frequently use this when you are using foreing langagues words in your text. So maybe we should not contradict this principle (that definitely ring a bell to me) and use __adada__ for the italic and skip the underline idea. This will be more logical for a typographical point of view. And it saves us the frequent case of http://mywonderfulurlwitha/andanother/ What do you think? _______________________________________________________ Reply to this item at: <http://gna.org/task/?func=detailitem&item_id=2874> _______________________________________________ Message posté via/par Gna! http://gna.org/ _______________________________________________ Savane-dev mailing list Savane-dev@gna.org https://mail.gna.org/listinfo/savane-dev
