Re: [WSG] convert to XHTML
Stuart Sherwood wrote: Hi Everyone, I'm wondering what is the best way to convert a large text file to XHTML? Preferably, I'd like the conversion to be performed to ignore styles, so the output is clean, semantic markup. I'd rather add my own stlying later. Textile! see http://www.textism.com/tools/textile/ and http://forum.textpattern.com/ Of course, that will assume you can go through and hand edit the plain text, but its really worth it. (I've been writing textile-based content for the last couple of weeks and hand coded some html-content this morning and went eww! eww! eww! all through it ;)) HIH! Lea -- Lea de Groot Brisbane, Australia ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Target attribute - coming or going?
I just had a look at an interesting article about using javascript instead of target to open new windows. http://www.456bereastreet.com/archive/200605/using_javascript_instead_of_target_to_open_new_windows/ In the comments below the article, there is various discussion including whether it is worth going to all this bother when you could just use target=_blank to open a new window, although using that means your site will not validate with a strict doctype. The one argument that may trump the other arguments is that there's a target property in the CSS3 Hyperlink module working draft. Does this mean that they have seen the error of removing the target attribute and are now bringing it back, in which case we should just keep using it and use a transitional doctype? Another thing that interested me in the comments was this, How about mobile devices, non-textual linux terminals (lynx)? What is the problem with using the target attribute with these devices? Thanks, Stephen ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Target attribute - coming or going?
On 5/4/06, Stevio [EMAIL PROTECTED] wrote: The one argument that may trump the other arguments is that there's a target property in the CSS3 Hyperlink module working draft. Does this mean that they have seen the error of removing the target attribute and are now bringing it back, in which case we should just keep using it and use a transitional doctype? The target property in css is not the same as the html attribute target. It can be confusing when they use the same terms but we have to live with it. What the target property in css does, it enables you to give style to anchor-elements. Dev edge has a good article about it, you can test examples out in Firefox (atleast). http://devedge-temp.mozilla.org/viewsource/2003/target-selector/index_en.html ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] frames for HTML
Michael Yeaney wrote:
While frames may be horrible for search engine crawling and
bookmarking, IMO they are a godsend for web-delivered rich
applications (i.e., when you don't want people jump in at random, and
you need to give the solid feel of a 'real' desktop app.)these
types of things aren't usually crawled by search engines though,
either. Some examples that come to mind are M$ Outlook Web Access
(even though it's only IE), CheckPoint firewall admin tools (all web
based), etc.
That said, I would NOT use them for public domain, accessible, content
delivery web sites (as mentioned in previous posts).
Just my $.02.
(Flame suit on)
Mike
Well I /would/, and indeed do! If the user is going to be moving about
a lot from one menu item to another, frames are brilliant. Yes, I know I
can emulate them with position-fixed, but it can be an awful mess to
maintain. Also, you can overcome the 'lost pages' problem by using
something like :
script type=text/javascript
if (parent.location.href == self.location.href){
window.location.href = 'frameset.html'
}
/script
at the top of each relevant page. Bookmarking is not a good point, as
has been said, but it isn't all that difficult for a person if the
bookmark takes them to the frameset instead of the page - it's only one
click, after all.
Lastly, I get many, (many), compliments on the simplicity of use of
http://www.raintreehouse.co.uk - and it's based on frames. Sometimes
(not always) the advantages far exceed the disadvantages.
(retires behind heat shield . . . ) :-)
--
Best Regards,
Bob McClelland
Cornwall (UK)
www.gwelanmor-internet.co.uk
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Target attribute - coming or going?
Nils Kr. Falch wrote: On 5/4/06, Stevio [EMAIL PROTECTED] wrote: The one argument that may trump the other arguments is that there's a target property in the CSS3 Hyperlink module working draft. Does this mean that they have seen the error of removing the target attribute and are now bringing it back, in which case we should just keep using it and use a transitional doctype? The target property in css is not the same as the html attribute target... What the target property in css does, it enables you to give style to anchor-elements. No, Stevio was not referring to the :target *pseudo-class* (that's not a property, it's a selector). Stevio was referring to the 'target' *property* in the CSS3 Hyperlink Presentation Module working draft [1], and that proposed property is designed to serve a similar purpose to the target attribute in HTML. [1] http://www.w3.org/TR/css3-hyperlinks/ -- Lachlan Hunt http://lachy.id.au/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] frames for HTML
Here are a couple experiments by Hedger Wang that you may find interesting. CSS Framesets (variations of these have been around forever) http://www.hedgerwow.com/360/dhtml/css-frameset/demo_1.html Drag and drop toolbars (this is really cool and gives you more of a desktop application experience) http://www.hedgerwow.com/360/dhtml/css-frameset/toolbar/demo.html Ted -Original Message- From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED] On Behalf Of Michael Yeaney Sent: Thursday, May 04, 2006 5:35 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] frames for HTML While frames may be horrible for search engine crawling andbookmarking, IMO they are a godsend for web-delivered richapplications (i.e., when you don't want people jump in at random, andyou need to give the solid feel of a 'real' desktop app.)thesetypes of things aren't usually crawled by search engines though,either. Some examples that come to mind are M$ Outlook Web Access(even though it's only IE), CheckPoint firewall admin tools (all webbased), etc. That said, I would NOT use them for public domain, accessible, contentdelivery web sites (as mentioned in previous posts). Just my $.02. (Flame suit on)Mikeyجr,_m ֧uݲ躟ym ֧uݲ躟j)zXz~gz'-x-^+- )i ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] ajax and validation
I like to look at the generated source code in the web developers toolbar and then pasting the code into a new page to test validation. The generated source code option is great at finding strange layout issues. Go to view source view generated source in the web developer toolbar From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED] On Behalf Of Michael Dale Sent: Thursday, May 04, 2006 4:51 AM To: wsg@webstandardsgroup.org Subject: [WSG] ajax and validation I've been playing with _javascript_ and XMLhttprequest a bit today and was wonder how does one go about validating a site that contains ajax elements. I've tried using firefox web developer and doing a Local HTML validation, but that seems to return only data before any element is made active/loaded. Any ideas? Thanks, Michael Dale.
Re: [WSG] ajax and validation
On 5/4/06, Daniel Champion [EMAIL PROTECTED] wrote: There's a View Generated Source function in the Web Developer Extension [1] which provides the current DOM tree source. You could copy and paste that into a validator. Beyond that I'm not aware of a 'validate generated source' option in any FF extension. This actually isn't a reliable technique, because the generated source is not equivalent to the actual HTML Firefox received; instead, it's a serialization of the error-corrected DOM Firefox used internally to render the page. -- May the forces of evil become confused on the way to your house. -- George Carlin ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Target attribute - coming or going?
No, Stevio was not referring to the :target *pseudo-class* (that's not a property, it's a selector). Stevio was referring to the 'target' *property* in the CSS3 Hyperlink Presentation Module working draft [1], and that proposed property is designed to serve a similar purpose to the target attribute in HTML. [1] http://www.w3.org/TR/css3-hyperlinks/ I kept my mouth shut about the hover pseudo-class, because it was just so convenient. But opening a new window through CSS? That's a bit too much of a mix of presentation and behavior for my taste. Seems we're just moving from (Structure/Presentation) + Behavior, to Structure + (Presentation/Behavior). ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Target attribute - coming or going?
On 5/4/06, Kenny Graham [EMAIL PROTECTED] wrote: I kept my mouth shut about the hover pseudo-class, because it was just so convenient. But opening a new window through CSS? That's a bit too much of a mix of presentation and behavior for my taste. Seems we're just moving from (Structure/Presentation) + Behavior, to Structure + (Presentation/Behavior). I stand corrected: Learn something new every day. I was a bit rash in my first post. Though it gives substance to my claim that it is confusing when they use similar names on html attributes, css properties and psuedo-classes. ;) And yes I know :target it is a pseudo-class, it was a case of bad wording when I called it a property, my bad. Otherwise I have to agree with Kenny, after looking through that draft. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Menu suggestions
I've used Transmenus from youngpup on a recent project and they worked perfectly. They were also really easy to implement and customize. Might be worth a look. BenOn 04/05/06, Stevio [EMAIL PROTECTED] wrote: I'm looking for your best suggestions for menus that can be used for bothvertical and horizontal drop down / fly out menus for navigation linkspurposes.Clean standards compliant coded menus, with or without _javascript_, whichever you prefer, works across browsers.What are you using?Thanks,Stephen**The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Target attribute - coming or going?
Lachlan Hunt wrote: Nils Kr. Falch wrote: On 5/4/06, Stevio [EMAIL PROTECTED] wrote: The one argument that may trump the other arguments is that there's a target property in the CSS3 Hyperlink module working draft. Does this mean that they have seen the error of removing the target attribute and are now bringing it back, in which case we should just keep using it and use a transitional doctype? The target property in css is not the same as the html attribute target... What the target property in css does, it enables you to give style to anchor-elements. No, Stevio was not referring to the :target *pseudo-class* (that's not a property, it's a selector). Stevio was referring to the 'target' *property* in the CSS3 Hyperlink Presentation Module working draft [1], and that proposed property is designed to serve a similar purpose to the target attribute in HTML. [1] http://www.w3.org/TR/css3-hyperlinks/ This reads like it's an admission that perhaps it was a bad idea to do away with the old target, so we'll design a new one that is better - but you'll have to wait n years before you can use it properly (when all browsers support CSS3). perhaps we should have kept the old target so the transition could be smooth, instead of causing a lot of folk a lot of headaches in the interim. We apologise for any inconvenience this has caused. :-) -- Best Regards, Bob McClelland Cornwall (UK) www.gwelanmor-internet.co.uk ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] convert to XHTML
I have recently been giving some HTML advice to a person that has done a web site in FrontPage. I have not looked at the code, however, knowing it is from Microsoft (M$) the code will be a real mess. Is their away to convert from FrontPage to something that is web standard? Or should I just start from square one? I haveDreamWaever 7.0 on my PC although I hand code. And free is preferable. Angus MacKinnon MacKinnon Crest Saying Latin - Audentes Fortuna Juvat English - Fortune Assists The Daring Web page http://www.infoforce-services.com Choroideremia Research Foundation Inc. 2nd Vice president http://www.choroideremia.org ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] content: .;
Sorry for the ignorant, but what is this for? I saw it in someone esle code sometimes ago and see it again in another site. content: .; ... It's the CSS 'content' property, explained here: http://www.w3.org/TR/CSS21/generate.html#content And this explains what is this for? part: http://positioniseverything.net/easyclearing.html Regards, Rimantas -- http://rimantas.com/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] ajax and validation
On 5/5/06, Ted Drake [EMAIL PROTECTED] wrote: I like to look at the generated source code in the web developers toolbar and then pasting the code into a new page to test validation. IIRC, there's a simpler way to do that. In web developer's toolbar under Tools, select Validate Local HTML (it's at the bottom of the list). No cutting/pasting/saving new files required. Cheers, Josh ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] content: .;
It's the CSS 'content' property, explained here: http://www.w3.org/TR/CSS21/generate.html#content And this explains what is this for? part: http://positioniseverything.net/easyclearing.html Thank you Paul and Rimantas :) tee ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Layout problem
Title: [WSG] Layout problem Hi, I am having problems with the main navigation for a site I am working on I have used an unordered list to achieve my nav structure, but I am having an issue with non-IE browsers and I was hoping someone could show me the error of my ways. You can view the page here: http://www.digitaldogma.com.au/clients/hoyne/bolinda/v3/ My problem is that the UL area (the main nav) seems to be moving above the height of its containing div (the grey background). Any idea as to what I am doing wrong? kind regards Adrian O'Hagan Multimedia Coordinator digitaldogma | MAKING CREATIVITY WORK Level 1, 244 Inkerman Street | St Kilda East 3183 Victoria Mob: 0408 768 343 | Tel: 03 9527 5055 | Fax: 03 9527 5099 [EMAIL PROTECTED] | http://www.digitaldogma.com.au This e-mail and any files transmitted with it are confidential and may contain privileged information. It is intended solely for the use of the individual or entity to whom it is addressed. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information in this e-mail. If you are not the intended recipient please notify [EMAIL PROTECTED]
Re: [WSG] convert to XHTML
At 02:01 PM 5/4/2006, Stuart Sherwood wrote: ... I'm wondering what is the best way to convert a large text file to XHTML? ... If it is a word processing document I open it in Open Office, save as HTML, then run through Tidy to clean up the markup and convert it to XHTML http://www.tomw.net.au/2006/wd/#ebook. Tidy has specific functions for cleaning up HTML generated by Ms-Word, but seems to work just as well with OOO. Tidy collects up all the formatting and puts it in a style sheet at the top of the document. I then cut this out and put it in a separate file, deleting any styles which are not needed. ps: If the document has images, save it in OOO format and then unzip that file. Alongside the XML of the text are the images. Tom Worthington FACS HLM [EMAIL PROTECTED] Ph: 0419 496150 Director, Tomw Communications Pty LtdABN: 17 088 714 309 PO Box 13, Belconnen ACT 2617http://www.tomw.net.au/ Director, ACS Communications Tech Board http://www.acs.org.au/ctb/ Visiting Fellow, ANU Blog: http://www.tomw.net.au/blog/atom.xml ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Layout problem
Title: Re: [WSG] Layout problem Thanks to Matt for the tip was most helpful. The issue is now resolved. Regards, Adrian. Hi, I am having problems with the main navigation for a site I am working on I have used an unordered list to achieve my nav structure, but I am having an issue with non-IE browsers and I was hoping someone could show me the error of my ways. You can view the page here: http://www.digitaldogma.com.au/clients/hoyne/bolinda/v3/ My problem is that the UL area (the main nav) seems to be moving above the height of its containing div (the grey background). Any idea as to what I am doing wrong? kind regards Adrian O'Hagan Multimedia Coordinator digitaldogma | MAKING CREATIVITY WORK Level 1, 244 Inkerman Street | St Kilda East 3183 Victoria Mob: 0408 768 343 | Tel: 03 9527 5055 | Fax: 03 9527 5099 [EMAIL PROTECTED] | http://www.digitaldogma.com.au This e-mail and any files transmitted with it are confidential and may contain privileged information. It is intended solely for the use of the individual or entity to whom it is addressed. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information in this e-mail. If you are not the intended recipient please notify [EMAIL PROTECTED]
[WSG] Copyright Question
** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
