Follow-up Comment #11, task #2874 (project savane):
> Frankly, I do not want to simply do test for this. We wont be
> able to check the 13000 items posted at LCG Savannah and we
> cannot publish a version that may alter inappropriately old
> item. So even if we do test and dont detect problems, we'll
> still have to add tags for the old item so they are not
> affected by the wiki formatting because they were not meant to
> be formatted this way.
Would it be an option to write a script that checks this and reports possible
problems? The admin could then fix those before upgrading. I imagine that
those errors will be only very few. That's why I'd like to run some tests on
the Savane DB. If it turns out that there are many problem cases, we must not
perform that markup.
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.
> Why not. But in this case, shouldn't we use double signs
> everywhere for cohesion sake?
Hm, we could do that. However, I like this *syntax* better than this
**syntax**. We could also allow both, since the single markup characters
already work ...
_______________________________________________________
Reply to this item at:
<http://gna.org/task/?func=detailitem&item_id=2874>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
