atw: Re: MS Publisher

The problem there I can see is if you want to add pages or change a font
size/colour/position and have it apply to the whole page or site, if
there are no style sheets, then you have to go through and do it all by
hand, line by line, instead of just clicking a button...

 

________________________________

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Christine Kent
Sent: Wednesday, 21 January 2009 2:55 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

 

Again, if WebCompiler doesn't care, why should I?  

 

Genuine question - if WebCompiler manages to compile a working
executable, what can go wrong after compilation?

 

Christine

 

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Rebecca
Caldwell
Sent: Wednesday, 21 January 2009 4:48 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

 

I would be more concerned at how publisher compiles CSS. The way I work
with WebPages/sites, I won't touch it unless the CSS is separated from
the code. I just showed someone how to use style sheets as they were
bamboozled as to why the page size was so big, turns out the inline
styles were longer than the page content! Never even occurred to me to
use publisher for this kind of thing though.

 

Rebecca

 

________________________________

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Deborah Cross
Sent: Wednesday, 21 January 2009 2:42 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

 

Seems I've hit a nerve, huh? Or perhaps I have not expressed myself
properly.

 

I was trying to help by pointing out that your final product might have
accessibility issues if it is generated through Publisher. 

 

Accessibility of information is no joke and can be quite costly, as
groups like SOCOG will attest to.

Accessible code is actually modern thinking. Standards like WCAG 1 and 2
are fundamental to ensuring that everyone has access to web content.

 

Given that I work in the web development industry, and am responsible
for implementing and coding web 2.0 (that's one 0) features, I'm not
concerned about being left behind nor taking the professional high
ground.

 

________________________________

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Christine Kent
Sent: Wednesday, 21 January 2009 2:19 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

Another thing you might want to consider is the usability and
accessibility of web code produced.

 

I don't have experience with Publisher, but if the HTML code it produces
is anything like MS Word, you could be in trouble.

 

Not an issue.  WebCompiler compiles the code into a locked down product
for which the source code can be made invisible.  If it succeeds in
compiling, then the code is OK - that's the sum total of it.

 

I think that we need to be a little bit careful that we are not left
behind taking the professional high ground, while the rest of the world
has raced ahead courtesy of Web 2.00, and all the program spin-offs from
Web 2.00 that are further enabling it.  Frankly, in this context, dirty
code is irrelevant. It is old thinking.

 

Christine

 

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Deborah Cross
Sent: Wednesday, 21 January 2009 2:10 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: MS Publisher

 

 

Some Publisher resources are available at
http://office.microsoft.com/en-us/publisher/HA012079251033.aspx

 

======================================= 
Deborah Cross 
E: deborah.cross@xxxxxxxxxx  
=======================================

Other related posts: