Has anyone found a way to have Dreamweaver (8) create valid
xHTML in library items? I have XHTML Strict as my default for new
documents in preferences, and the all doctypes etc… in the site
itself set similarly, but in Library items in WYSIWYG mode
line-breaks and image tags are written HTML4 style (<br>,
<img>) not as xHTML (<br />, <img />). This means
the library items insert non-valid code into the pages.|||
How are you creating your Library items? The traditional way
would be to
select something on an existing page and add it to the
Library. If the
existing page has proper syntax, so with the resulting
Library item.
–
Murray — ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don’t LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com – DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
“SDennis” <webforumsuser@macromedia.com> wrote in
message
news:eicl6f$dl3$1@forums.macromedia.com…
> Has anyone found a way to have Dreamweaver (8) create
valid xHTML in
> library
> items? I have XHTML Strict as my default for new
documents in preferences,
> and
> the all doctypes etc… in the site itself set
similarly, but in Library
> items
> in WYSIWYG mode line-breaks and image tags are written
HTML4 style (<br>,
> <img>) not as xHTML (<br />, <img />).
This means the library items insert
> non-valid code into the pages.
>
|||
Hi Murray,
Sorry, I should have been clearer. It’s only an issue when
editing an existing library item and adding an image or
line-break). It doesn’t seem to make any difference if the item was
originally created with/from xHTML.
I don’t have a huge problem with it personally, as knowing it
happens I just tidy up the code manually. But we have a couple of
clients who use Dreamweaver to maintain sites, and sometimes less
experienced team-members who aren’t aware of the problem. I wanted
to check I wasn’t missing some setting somewhere which would toggle
doctype for library items. If there isn’t anything which does this,
I may submit a bug/feature request about it.|||
> Sorry, I should have been clearer. It’s only an issue
when editing an
> existing
> library item and adding an image or line-break). It
doesn’t seem to make
> any
> difference if the item was originally created with/from
xHTML.
I see. That’s correct, once you have created the Library item
it loses its
association with the creating page’s doctype.
> I may submit a bug/feature request about it.
Please do. I could see this working similarly to how
Design-time
stylesheets work. The link is here -
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
–
Murray — ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don’t LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com – DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
“SDennis” <webforumsuser@macromedia.com> wrote in
message
news:eicr15$k19$1@forums.macromedia.com…
> Hi Murray,
>
> Sorry, I should have been clearer. It’s only an issue
when editing an
> existing
> library item and adding an image or line-break). It
doesn’t seem to make
> any
> difference if the item was originally created with/from
xHTML.
>
> I don’t have a huge problem with it personally, as
knowing it happens I
> just
> tidy up the code manually. But we have a couple of
clients who use
> Dreamweaver
> to maintain sites, and sometimes less experienced
team-members who aren’t
> aware
> of the problem. I wanted to check I wasn’t missing some
setting somewhere
> which
> would toggle doctype for library items. If there isn’t
anything which does
> this, I may submit a bug/feature request about it.
>
Related posts:
- Deleting unused Library items is incomplete
- library items
- Jumping to library items using keyboard shortcuts
- relative referencing using library items
- Multiple Body tags error when using library items
Related posts brought to you by Yet Another Related Posts Plugin.
