Re: WYSIWYG content development (was Re: RethinkingBrands)

>I have to admit that I don't quite understand the above use of the
>term WYSIWYG;
>   <http://en.wikipedia.org/wiki/WYSIWYG>
>I was under the impression that WYSIWYG is a property of the software,
>not the markup language. You can type HTML markup with a text editor,
>or use a WYSIWYG editor to create it from your What-You-See layout.

By WYSIWYG, people mean that HTML is typically relative and the layout of a 
webpage may be different depending on a number of factors. To a small 
degree, webpages will render different browsers, but even in the same 
browser the webpage will render differently when the browser is resized, 
etc. For a great example of "what you see is not what you get", try to print 
a webpage, and compare the printout to what you see on your computer screen: 
The page needs to be re-rendered to fit onto a piece of paper (especially if 
you print in "portrait", not "landscape").

>Instead of going through too much pain developing a tool to convert
>MW-markup into LaTeX, why don't we just see if modifying the printing
>style-sheet is sufficient for our needs?

That's the approach that i've been taking, personally. I've done some work 
on some printing templates that help to format a printed book, but don't 
look so good on the screen (how do you render a page break on the computer 
screen?). I think that there is alot that we could do straight from the 
HTML, if we avoid things that don't work when printed, and if we are willing 
to do the work to implement the proper styles for printing.

--Andrew Whitworth

_________________________________________________________________
PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
Live Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507

_______________________________________________
Textbook-l mailing list
[email protected]
http://lists.wikimedia.org/mailman/listinfo/textbook-l