1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6 <meta name="generator" content="Movable Type 5.2.3" />
8 <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
9 <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
10 <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
12 <title>Status for Andrew DeFaria: April 15, 2007 - April 21, 2007 Archives</title>
14 <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
15 <link rel="prev" href="http://defaria.com/blogs/Status/archives/week_2007_04_08.html" title="April 8, 2007 - April 14, 2007" />
16 <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2007_04_29.html" title="April 29, 2007 - May 5, 2007" />
18 <body class="layout-one-column">
20 <div id="container-inner" class="pkg">
23 <div id="banner-inner" class="pkg">
24 <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
25 <h2 id="banner-description">Searchable status reports and work log</h2>
30 <div id="pagebody-inner" class="pkg">
32 <div id="alpha-inner" class="pkg">
34 <p class="content-nav">
35 <a href="http://defaria.com/blogs/Status/archives/week_2007_04_08.html">« April 8, 2007 - April 14, 2007</a> |
36 <a href="http://defaria.com/blogs/Status/">Main</a>
37 | <a href="http://defaria.com/blogs/Status/archives/week_2007_04_29.html">April 29, 2007 - May 5, 2007 »</a>
42 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
43 xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
44 xmlns:dc="http://purl.org/dc/elements/1.1/">
46 rdf:about="http://defaria.com/blogs/Status/archives/week_2007_04_15.html#entry-000634"
47 trackback:ping="http://defaria.com/mt/mt-tb.cgi/23"
48 dc:title="Why MS Word is a bad HTML editor"
49 dc:identifier="http://defaria.com/blogs/Status/archives/week_2007_04_15.html#entry-000634"
50 dc:subject="Texas Instruments"
51 dc:description=" Described a little bit about why MS Word is not a good HTML editor..."
53 dc:date="2007-04-21T20:56:37-06:00" />
58 <h2 class="date-header">April 21, 2007</h2>
60 <div class="entry" id="entry-634">
61 <h3 class="entry-header">Why MS Word is a bad HTML editor</h3>
62 <div class="entry-content">
63 <div class="entry-body">
65 <li>Described a little bit about why MS Word is not a good HTML editor</li>
68 <p>LeGrand, Christina wrote:</p>
70 <blockquote type=cite>
71 <p>Larry, thanks for the great feedback! I have made the last three changes listed here - to the wording in the "Just the FAQs" section, the "ITS
72 in the Customer Success Story, and the URL in the LDM docs section. Great catches! For the first two suggestions, all secondary titles are Arial 11, so I am not sure why they look different in your Outlook, but I believe you that they do. If anyone knows of how to prevent this, please let me know!</p>
75 The proper way to "prevent" such things is to use the proper way to do
76 such things. To do this one should follow the standards and then
77 validate (as Regan said to Gorbachev "<a
78 href="http://www.brainyquote.com/quotes/quotes/r/ronaldreag147717.html">Trust
81 HTML headers should be done with the "H" tags of which there are H1 -
82 H6. IOW one should not be putting any kinds of font information such as
83 Arial nor point size in there. Such presentation information is best
84 left to the eventual reader, who may not have the font you've chosen
85 nor want Wingbats in Pink at 24 point! <br>
87 However if you must code in a layout that's what CSS is for.<br>
89 In any event Word, which this was made with, is an absolutely horrible
90 HTML editor! And I shall now show you some of the reasons why. I hope
91 you'll enjoy this ride as much as I will...<br>
93 First off MS Word created HTML pages contain a lot of bloat. What Word
94 does is include styling information at the beginning of the document to
95 cover MS Word "styles" then applies "styles" to the layout. This is
96 done, AFAICT, to attempt to get the web page to look "just like it did
97 in Word". In a sentence - It's bad web design and bloat to your web
98 pages let alone often non-standard and should be avoided at all costs.<br>
100 Here is the beginning bloat:<br>
102 <pre id="line165"><html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
103 xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
104 xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
105 xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
106 xmlns=3D<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/TR/REC-html40">"http://www.w3.org/TR/REC-html40"</a>>
110 <meta http-equiv=3DContent-Type content=3D"text/html; =
111 charset=3Dus-ascii">
112 <meta name=3DProgId content=3DWord.Document>
113 <meta name=3DGenerator content=3D"Microsoft Word 11">
114 <meta name=3DOriginator content=3D"Microsoft Word 11">
115 <link rel=3DFile-List href=3D<a class="moz-txt-link-rfc2396E" href="cid:filelist.xml@01C78350.D624B260">"cid:filelist.xml@01C78350.D624B260"</a>>
116 <link rel=3DEdit-Time-Data href=3D<a class="moz-txt-link-rfc2396E" href="cid:editdata.mso">"cid:editdata.mso"</a>>
120 v\:* {behavior:url(#default#VML);}
121 o\:* {behavior:url(#default#VML);}
122 w\:* {behavior:url(#default#VML);}
123 .shape {behavior:url(#default#VML);}
125 <pre id="line238"></style>
126 <![endif]--><o:SmartTagType
127 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
130 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
131 name=3D"PlaceType"/>
133 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
134 name=3D"PlaceName"/>
136 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
140 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
141 name=3D"PersonName"/>
142 <!--[if gte mso 9]><xml>
143 <o:OfficeDocumentSettings>
144 <o:DoNotRelyOnCSS/>
145 </o:OfficeDocumentSettings>
146 </xml><![endif]--><!--[if gte mso 9]><xml>
147 <w:WordDocument>
148 <w:SpellingState>Clean</w:SpellingState>
149 <w:DocumentKind>DocumentEmail</w:DocumentKind>
150 <w:EnvelopeVis/>
151 <w:ValidateAgainstSchemas/>
152 <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
153 <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
154 <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
155 <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
156 </w:WordDocument>
158 <pre id="line269"></xml><![endif]--><!--[if gte mso 9]><xml>
159 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
160 </w:LatentStyles>
162 </xml><![endif]--><!--[if !mso]>
164 st1\:*{behavior:url(#default#ieooui) }
169 /* Font Definitions */
172 panose-1:2 11 6 4 3 5 4 4 2 4;
173 mso-font-alt:Verdana;
175 mso-generic-font-family:swiss;
176 mso-font-pitch:variable;
177 mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
178 /* Style Definitions */
179 p.MsoNormal, li.MsoNormal, div.MsoNormal
180 {mso-style-parent:"";
182 margin-bottom:.0001pt;
183 mso-pagination:widow-orphan;
185 font-family:"Times New Roman";
186 mso-fareast-font-family:"Times New Roman";
188 a:link, span.MsoHyperlink
190 text-decoration:underline;
191 text-underline:single;}
192 a:visited, span.MsoHyperlinkFollowed
194 text-decoration:underline;
195 text-underline:single;}
197 {mso-margin-top-alt:auto;
199 mso-margin-bottom-alt:auto;
201 mso-pagination:widow-orphan;
203 font-family:"Times New Roman";
204 mso-fareast-font-family:"Times New Roman";
206 p.newslettertitle, li.newslettertitle, div.newslettertitle
207 {mso-style-name:newslettertitle;
208 mso-margin-top-alt:auto;
210 mso-margin-bottom-alt:auto;
212 mso-pagination:widow-orphan;
214 font-family:"Times New Roman";
215 mso-fareast-font-family:"Times New Roman";
217 p.newslettertext, li.newslettertext, div.newslettertext
218 {mso-style-name:newslettertext;
219 mso-margin-top-alt:auto;
221 mso-margin-bottom-alt:auto;
223 mso-pagination:widow-orphan;
225 font-family:"Times New Roman";
226 mso-fareast-font-family:"Times New Roman";
228 p.newsletterheading, li.newsletterheading, div.newsletterheading
229 {mso-style-name:newsletterheading;
230 mso-margin-top-alt:auto;
232 mso-margin-bottom-alt:auto;
234 mso-pagination:widow-orphan;
236 font-family:"Times New Roman";
237 mso-fareast-font-family:"Times New Roman";
239 p.newsletterbullet, li.newsletterbullet, div.newsletterbullet
240 {mso-style-name:newsletterbullet;
241 mso-margin-top-alt:auto;
243 mso-margin-bottom-alt:auto;
245 mso-pagination:widow-orphan;
247 font-family:"Times New Roman";
248 mso-fareast-font-family:"Times New Roman";
251 {mso-style-type:personal;
252 mso-style-noshow:yes;
253 mso-ansi-font-size:10.0pt;
254 mso-bidi-font-size:10.0pt;
256 mso-ascii-font-family:Arial;
257 mso-hansi-font-family:Arial;
258 mso-bidi-font-family:Arial;}
260 {mso-style-type:personal;
261 mso-style-noshow:yes;
262 mso-ansi-font-size:10.0pt;
263 mso-bidi-font-size:10.0pt;
265 mso-ascii-font-family:Arial;
266 mso-hansi-font-family:Arial;
267 mso-bidi-font-family:Arial;
270 {mso-style-type:personal;
271 mso-style-noshow:yes;
272 mso-ansi-font-size:10.0pt;
273 mso-bidi-font-size:10.0pt;
275 mso-ascii-font-family:Arial;
276 mso-hansi-font-family:Arial;
277 mso-bidi-font-family:Arial;
280 {mso-style-type:personal-reply;
281 mso-style-noshow:yes;
282 mso-ansi-font-size:10.0pt;
283 mso-bidi-font-size:10.0pt;
285 mso-ascii-font-family:Arial;
286 mso-hansi-font-family:Arial;
287 mso-bidi-font-family:Arial;
294 margin:1.0in 1.25in 1.0in 1.25in;
295 mso-header-margin:.5in;
296 mso-footer-margin:.5in;
303 <!--[if gte mso 10]>
305 /* Style Definitions */=20
307 {mso-style-name:"Table Normal";
308 mso-tstyle-rowband-size:0;
309 mso-tstyle-colband-size:0;
310 mso-style-noshow:yes;
312 mso-padding-alt:0in 5.4pt 0in 5.4pt;
314 mso-para-margin-bottom:.0001pt;
315 mso-pagination:widow-orphan;
317 font-family:"Times New Roman";
318 mso-ansi-language:#0400;
319 mso-fareast-language:#0400;
320 mso-bidi-language:#0400;}
322 <pre id="line430"></style>
323 <![endif]--><!--[if gte mso 9]><xml>
324 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
325 </xml><![endif]--><!--[if gte mso 9]><xml>
326 <o:shapelayout v:ext=3D"edit">
327 <o:idmap v:ext=3D"edit" data=3D"1" />
328 </o:shapelayout></xml><![endif]-->
333 Now wasn't that fun? <span class="moz-smiley-s1"><span> :-) </span></span><br>
335 After creating all that crud we are now able to apply it to our
336 content. Here's the part that does the heading:<br>
337 <blockquote><tt> <p class=3Dnewsletterheading =<br>
338 style=3D'mso-margin-top-alt:0in;margin-right:<br>
339 0in;margin-bottom:4.0pt;margin-left:0in'><span =<br>
340 style=3D'mso-bookmark:OLE_LINK1'><span<br>
341 style=3D'mso-bookmark:OLE_LINK10'><span =<br>
342 style=3D'mso-bookmark:OLE_LINK11'><span<br>
343 style=3D'mso-bookmark:OLE_LINK12'><span =<br>
344 style=3D'mso-bookmark:OLE_LINK2'><span<br>
345 style=3D'mso-bookmark:OLE_LINK3'><strong><b><font
348 face=3DArial><span =<br>
349 style=3D'font-size:12.0pt;font-family:Arial;mso-bidi-font-style:<br>
350 italic'>DesignSync Documentation Has
351 Moved</span></font><span<br>
353 style=3D'mso-bidi-font-style:italic'><o:p></o:p></span></b></strong></spa=<br>
354 n></span></span></span></span></span></p><br>
356 OK, not you tell me - where's the Arial 11 point in there?<br>
359 I'm sure you've enjoyed the above exercise...<br>
361 Oh, and how does this look in "straight" HTML?<br>
362 <blockquote><tt><h2>DesignSync Documentation Has Moved</h2></tt><br>
366 <p class="entry-footer">
367 <span class="post-footers">Posted by at 8:56 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000634.html">Permalink</a>
369 | <a href="http://defaria.com/blogs/Status/archives/000634.html#trackback">TrackBacks (0)</a>
376 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
377 xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
378 xmlns:dc="http://purl.org/dc/elements/1.1/">
380 rdf:about="http://defaria.com/blogs/Status/archives/week_2007_04_15.html#entry-000633"
381 trackback:ping="http://defaria.com/mt/mt-tb.cgi/22"
382 dc:title="Turning on HTML for Exchange/IMAP"
383 dc:identifier="http://defaria.com/blogs/Status/archives/week_2007_04_15.html#entry-000633"
384 dc:subject="Texas Instruments"
385 dc:description=" Described how to configure Exchange's IMAP server to server out HTML..."
387 dc:date="2007-04-21T20:38:56-06:00" />
394 <div class="entry" id="entry-633">
395 <h3 class="entry-header">Turning on HTML for Exchange/IMAP</h3>
396 <div class="entry-content">
397 <div class="entry-body">
399 <li>Described how to configure Exchange's IMAP server to server out HTML</li>
402 <p>I had worked on this before but I just want to document it here. I use Thunderbird and connect to Exchange servers via IMAP. Here at TI I was only getting plain text from the IMAP server. I was speaking to a friend of mine who managed an Exchange at a prior company we worked together at. I used TB and IMAP back then too and did not have problems with HTML'ized email from Outlook users:</p>
404 <b><font color="#204a87">Andrew DeFaria:</font></b> In any event I'm nore interested if you have an answer to my question regarding Exchange/IMAP.<br>
405 <b><font color="#204a87">Andrew DeFaria:</font></b> How do you configure Exchange to sent HTML email to IMAP?<br>
406 <b><font color="#cc0000">Ron Van Scherpe:</font></b> as far as imap goes,<br>
407 <b><font color="#cc0000">Ron Van Scherpe:</font></b> we don't use it here.<br>
408 <b><font color="#cc0000">Ron Van Scherpe:</font></b> but lemme check something<br>
409 <b><font color="#204a87">Andrew DeFaria:</font></b> I could have sworn that while at Salira I used TB and IMAP to your exchange server and when Outlook users sent HTML'ized email I saw it in TB as HTML'ized.<br>
410 <b><font color="#204a87">Andrew DeFaria:</font></b> Here at TI all I get from the IMAP port is just plain text. Seems to me that this might be an Exchange setting....<br>
411 <b><font color="#cc0000">Ron Van Scherpe:</font></b> yes..it's a server setting.<br>
412 <b><font color="#cc0000">Ron Van Scherpe:</font></b> they must have it set for plain text only because you have 3 options..<br>
413 <b><font color="#cc0000">Ron Van Scherpe:</font></b> plain text, HTML or both.<br>
414 <b><font color="#cc0000">Ron Van Scherpe:</font></b> we have it set to both here<br>
415 <b><font color="#cc0000">Ron Van Scherpe:</font></b> and we did at Salira.<br>
416 <b><font color="#cc0000">Ron Van Scherpe:</font></b> they're taking an MS approach<br>
417 <b><font color="#cc0000">Ron Van Scherpe:</font></b> they don't want HTML rendered hacks<br>
418 <b><font color="#204a87">Andrew DeFaria:</font></b> HTML rendered hacks will happen more often in Outlook than TB is my guess.<br>
419 <b><font color="#cc0000">Ron Van Scherpe:</font></b> login in to the Exchange server<br>
420 <b><font color="#cc0000">Ron Van Scherpe:</font></b> open up ESM<br>
421 <b><font color="#cc0000">Ron Van Scherpe:</font></b> expand the server so that you see the Protocols...<br>
422 <b><font color="#cc0000">Ron Van Scherpe:</font></b> right click on the iMap virtual server and select properities<br>
423 <b><font color="#cc0000">Ron Van Scherpe:</font></b> click on the message format tab and select rendering type<br>
424 <b><font color="#cc0000">Ron Van Scherpe:</font></b> you'll have to restart the imap server<br>
425 <b><font color="#204a87">Andrew DeFaria:</font></b> Great! And thanks! I'll send this along...<br>
426 <b><font color="#204a87">Andrew DeFaria:</font></b> I owe you a beer (that is if they agree to it and implement it...)<br>
427 <b><font color="#cc0000">Ron Van Scherpe:</font></b> $50<br>
428 <b><font color="#204a87">Andrew DeFaria:</font></b> OK a case!<br>
429 <b><font color="#cc0000">Ron Van Scherpe:</font></b> heh</p>
432 <p class="entry-footer">
433 <span class="post-footers">Posted by at 8:38 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000633.html">Permalink</a>
435 | <a href="http://defaria.com/blogs/Status/archives/000633.html#trackback">TrackBacks (0)</a>
442 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
443 xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
444 xmlns:dc="http://purl.org/dc/elements/1.1/">
446 rdf:about="http://defaria.com/blogs/Status/archives/week_2007_04_15.html#entry-000632"
447 trackback:ping="http://defaria.com/mt/mt-tb.cgi/21"
448 dc:title="Oracle limit clause"
449 dc:identifier="http://defaria.com/blogs/Status/archives/week_2007_04_15.html#entry-000632"
451 dc:description=" Modify site almost functionally complete Looking into how to do what MySQL does with it's limit clause in Oracle..."
453 dc:date="2007-04-18T19:04:09-06:00" />
458 <h2 class="date-header">April 18, 2007</h2>
460 <div class="entry" id="entry-632">
461 <h3 class="entry-header">Oracle limit clause</h3>
462 <div class="entry-content">
463 <div class="entry-body">
465 <li>Modify site almost functionally complete</li>
467 <li>Looking into how to do what MySQL does with it's limit clause in Oracle</li>
470 <h2>Oracle limit clause</h2>
472 <p>Found this ugly workaround for MySQL's limit clause:</p>
474 <div class=code><pre>
476 select rownum as limit, t.* from (
477 select * from <table> where <condition>
479 t) where limit between <lower limit> and <upper limit>
482 <p>Hey it works....</p>
484 <p class="entry-footer">
485 <span class="post-footers">Posted by at 7:04 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000632.html">Permalink</a>
487 | <a href="http://defaria.com/blogs/Status/archives/000632.html#trackback">TrackBacks (0)</a>