Re: [WSG] Web governance
Here I am writing from the other side of the fence. I find that some of the barriers to communication are rooted in the two different 'cultures' of the two streams. I recently had to work with a admittedly junior web developer to upgrade static HTML pages associated with a web application which my group supports. I mentioned to him that if he intended to change file structure he needed to let me know right away so I could make parallel adjustments on the application side. Silence for 1 month followed by the return of the revised files in a completely new file structure with all the the testing environment dependent links changes to hard coded production links. When challenged, he criticized the IT side for the slowness of posting time. After all their web designers aim to get their changes made to production in under 24 hours from the time they are requested. SO... the whole job had to be done again - old file structure restored, testing environment dependent links restored - and you can guess it wasn't the 'web guy' doing it :) These are the experiences that poison the well for worthwhile co-operation. Both sides have stuff to learn from each other. I feel fortunate that I have a foot on each horse. Somedays that spangled suit I am wearing just doesn't seem that glamourous when trying to explain to either side why they insist on doing things differently from each other when judged by their own experiences it is patently unnecessary. Agh. Thanks for listening. Climbing down from my soapbox now :) Mary Krieger *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Making PDF and Word files accessible
At 05:36 AM 6/3/2005, you wrote: snip Secondly, with the Word documents, if there is an easier way to convert them to HTML? At the moment I am saving as HTML from Word, taking them into Dreamweaver and using 'Clean up Word HTML'. After that I use 'Find and replace' to strip out all font, span and attributes from p such as class and style. At which point I still have to mark up the document with proper headings, bulleted lists, etc. A little time-consuming and fiddly to say the least! Am I doing this right or is there another way to make these files accessible? (and make my life easier, after all it is Friday :-) ) Angela Angela Galvin Worth Media 15-17 Middle Street Brighton BN1 1AL T: 01273 201149 F: 01273 710004 - www.worthmedia.net I would skip the part where you save from Word into HTML. Why give yourself the grief? If you copy and paste the text into the 'content' part of your standard page, the line breaks will show you where the paragraph and headings are. I'm using Homesite so I just select and repeat the similar code ( first p, then h1, h2 etc) from one end of the document to the other. Generally the only thing missing them is the the use of bold and italic within the text (not part of the heading structure) and any tables or lists within the text. Validate to catch any stray weirdness and on to the next. Perhaps not the most interesting type of web coding but listening to music of your taste, you can work up a good rhythm and code a whack of stuff relatively cleanly. Not a bad way to spend a Friday. Mary Krieger Winnipeg Manitoba Canada http://www.mts.net/~mkrieger ** 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] pt, em and ex
Greetings, As Marilyn notes, CSS has inherited a technical vocabulary from another technology - typography. In that world... - The point (pt) size tells the printer how big is the distance from the top of the ascender to the bottom of the descender for that font. - An em is equal to the height of the font being used ( or in other words the point size). It is used to set the widths and height of other elements on the page that relate to the font placement. (indent at the beginning of paragraphs, etc.) - The X-height is the height of a letter excluding the ascenders and descenders. Different type faces have different ratios between the height of the letters and the width of the letters. The ratio between the pt and x-height illuminates that relationship. Em dashes and en dashes are the appropriate lengths dependant on the pt size of the font. Note that both the pt and x-height are descriptors of a particular font but the em is a relative unit used to design the page based on what font is selected. X-height was little used by printers and typesetters. It was more important to the designer of the typeface and to the person who selected which typeface was to be used for a particular job. In CSS, the terms are defined as - ems is the height of the element's font - x-height is the height of the letter 'x' In CSS both ems and ex are relative units based on what font is being used. In a way, font size:10pt; is not selecting at what size you wish to see the letters but a way of selecting a particular font. It could be that in the future, we will have a wider variety of typefaces available to use on the web, some of which will have differing body and ascender ratios. Web designers may then find the ability to use ex as well as em more useful than we do now. Mary Krieger Winnipeg MB Canada http://www.mts.net/~mkrieger/ ** 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[2]: [WSG] pt, em and ex
Barring browser weirdness for a brief utopian moment, is this the way it is supposed to work.? In order for any text to appear, someone somewhere has to have chosen a font face and size. So choosing to use relative rather than absolute units for font size moves where the decision occurs. If the stylesheet belonging to the page uses an absolute unit like pt to set the size of the base font, the browser will attempt to use the page's stylesheet to set the default font size. If the stylesheet belonging to the page instead uses the relative unit % or ems to set the size of the base font, then the browser will set the default font size relative to the local machine's default stylesheet's font size. Here 1 em behaves the same way as 100%. If the stylesheet belonging to the page instead uses the relative unit px to set the size of the base font, then the browser will set the default font size relative to the local machine's resolution. If the remainder of the font-sizes in the stylesheet are set with relative units, the page should retain the size relationships of the page's stylesheet no matter where the decision about default font size occurs. Mary Krieger Winnipeg MB Canada http://www.mts.net/~mkrieger/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
