Florent André schrieb:
On Mon, 25 May 2009 14:29:24 +0200, Andreas Hartmann <andr...@apache.org>
wrote:
Anish schrieb:
The effect of the attributes like border, vspace, hspace can easily be
achieved by using CSS, eg. by giving the img element a class (or an
id) attribute:
Thanks Rainer.
Actually I was looking to achieve these attributes thro' TinyMCE
directly.
But using CSS sounds better..... :-)
Yes, it is important that the content doesn't contain any style
information.
http://en.wikipedia.org/wiki/Separation_of_presentation_and_content
I'm totally agree with this principle, but how can we do if we want to
allow each end-user to define his presentation for his article :
>
- end-userA want to have a 30*200 px centered image with no-border
- end-userB want a 50*50px align right with 3px border
- etc...
The short answer: Don't allow it :)
A key to the solution is making the content format(s) flexible enough to
support all major usage scenarios from a semantic point of view. For
instance, provide different types of image inclusion, which have a
different meaning and can be styled differently:
* <image>
* <figure>
* <chart>
Another key is providing multiple presentation styles for those who need
(or want) layout choices.
Allow this would says :
1/ each article as his proper CSS
2/ Lenya have a mechanism to translate WYSIWYG editor presentation to CSS
(it's difficult to say to end-user : write your CSS !)
In my experience, most users don't want to make their own design. But it
helps to give them options (e.g., a combobox to select a style for the
complete page). This way you can still ensure that all rendered pages
conform to your CI guidelines.
Two remarks :
1/ Allow end-user to do all what he want on presentation can be very worth
to the "graphical unity" of the site (just few controlled styles is good
for ensure unity)... but we all like to have a self-love good presentation
article...
I'm afraid don't quite understand this …
-- Andreas
2/ I don't really study editors for now, so maybe I says some enormous
mistake ! :)
Regards
-- Andreas
Rainer Schöpf wrote:
Hi Anish,
> Thanks Rainer, now it's working. I've applied the patch to
*/tiny_config.js/*
> > Now it doesn't throw any exception when I add border,
> > vspace,hspace
> attributes. But these attributes are not getting reflected in the
image tag
> (after saving).
> > Should they or not as these are deprecated?
These attributes deprecated in HTML 4.01, and not allowed in XHTML.
By default, lenya uses the XHTML basic schema (see
http://www.w3.org/2007/09/dtd-comparison.html
for a comparison to other XHTML schemas.) The problem with the default
setup for TinyMCE is that is can produce XHTML tags and attributes
that are not allowed in XHTML basic. With the changes, TinyMCE removes
all these invalid elements and attributes. Otherwise, you get the
exceptions when the editor returns the page to lenya and the schema
validation finds invalid tags or attributes.
You could use another schema, like XHTML Strict, but you will have the
same problem: if the editor generates tags/attributes that are
rejected by the schema validator, you see the exceptions.
The effect of the attributes like border, vspace, hspace can easily be
achieved by using CSS, eg. by giving the img element a class (or an
id) attribute:
<img class="img-type-a" .. />
and specifying, eg.
img.img-type-a {
border-width: 1px solid black;
}
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org
For additional commands, e-mail: user-h...@lenya.apache.org
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org
For additional commands, e-mail: user-h...@lenya.apache.org
