Eirik,
On 2010-09-15 15:11, Eirik Schwenke wrote:
2. WikiFromatter doesn't respect html special chars - i.e.
become  - is it a bug or expected behavior? (I wrote a
plugin to workaround it - but I think it should be fixed)
AFAIK wiki text is "unrealated" to html, "formatting" the wikitext
before processing sounds like a pretty bad idea to me.
If you are maintaining true multilingual environment time to time you
have to enter some unicode characters directly. is just on of
examples, other common case is angle quotes (guillemets)
«/»
What notation is used to achieve it doesn't really matter
i.e. is \u171 for « is also acceptable.
And I pretty sure trac should support it in default wiki formatter.
4. Wiki paragraph text have to have come default class i.e.<p
class="wikitext"> ....</p> otherwise it's hard to manage fonts etc
within wiki.
From the source at eg:
http://trac.edgewall.org/wiki/WikiFormatting
I see:
<div id="wikipage"><p> (the div surronds the page content).
Wouldn't ".wikipage p" work? Or ".wikipage> p" ?
#wikipage p {
}
works, but separate class cost nothing and it makes a live a little bit
better especially if you have to do something with it by JavaScript.
Regards,
-Dmitry
--
Dmitry Samersoff
[email protected], http://devnull.samersoff.net
* I do want to change the world, I don't want the world to change me
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
