Comments on: Google Docs and the <string> tag http://www.elharo.com/blog/software-development/xml/2007/02/01/google-docs-and-the-string-tag/ Ranting and Raving Thu, 08 Jan 2009 17:09:45 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Ed Davies http://www.elharo.com/blog/software-development/xml/2007/02/01/google-docs-and-the-string-tag/comment-page-1/#comment-39681 Ed Davies Fri, 02 Feb 2007 20:11:47 +0000 http://www.elharo.com/blog/software-development/xml/2007/02/01/google-docs-and-the-string-tag/#comment-39681 Sort of related: the title of this page shows the word "string" neatly wrapped in angle brackets just like a well behaved HTML/XML tag. On Cafe au Lait, however, it shows with an ugly mess of character entities before and after it. Looking at the source it appears some ampersands got escaped when they shouldn't have. Is this not slightly embarrasing (though perhaps not quite as much as it would be on Cafe con Leche)? As for the quoted source in this article: I'm not sure what you mean was originally there - the word "string" appears twice, once initial capped and once not... Sort of related: the title of this page shows the word “string” neatly wrapped in angle brackets just like a well behaved HTML/XML tag.

On Cafe au Lait, however, it shows with an ugly mess of character entities before and after it. Looking at the source it appears some ampersands got escaped when they shouldn’t have. Is this not slightly embarrasing (though perhaps not quite as much as it would be on Cafe con Leche)?

As for the quoted source in this article: I’m not sure what you mean was originally there - the word “string” appears twice, once initial capped and once not…

]]> By: mike nicholaides http://www.elharo.com/blog/software-development/xml/2007/02/01/google-docs-and-the-string-tag/comment-page-1/#comment-39289 mike nicholaides Thu, 01 Feb 2007 17:53:14 +0000 http://www.elharo.com/blog/software-development/xml/2007/02/01/google-docs-and-the-string-tag/#comment-39289 maybe it's something that their XSL stylesheet didn't take care of properly? maybe it’s something that their XSL stylesheet didn’t take care of properly?

]]>