<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/wordpress-mu-1.2.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Open Road</title>
	<link>http://blogs.openroad.net.au</link>
	<description>Exploring diversity on the Web</description>
	<pubDate>Mon, 19 May 2008 03:18:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.1</generator>
	<language>en</language>
			<item>
		<title>Burmese OpenOffice</title>
		<link>http://blogs.openroad.net.au/2008/05/19/burmese-openoffice/</link>
		<comments>http://blogs.openroad.net.au/2008/05/19/burmese-openoffice/#comments</comments>
		<pubDate>Mon, 19 May 2008 03:16:39 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Development]]></category>

		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2008/05/19/burmese-openoffice/</guid>
		<description><![CDATA[A Burmese localisation project for OpenOffice has been established and is under way. The Burmese OpenOffice is based on the Unicode 5.1 Myanmar block. The localisation team are looking for beta testers.
A translation project has been set up to translate OpenOffice interface into Burmese. The Burmese translation project are looking for volunteers.
Other projects that are [...]]]></description>
			<content:encoded><![CDATA[<p>A Burmese localisation project for OpenOffice has been established and is under way. The <a href="http://my.openoffice.org/">Burmese OpenOffice</a> is based on the Unicode 5.1 Myanmar block. The localisation team are looking for beta testers.</p>
<p>A translation project has been set up to translate OpenOffice interface into Burmese. The <a href="http://www.sunvirtuallab.com:32300/my/">Burmese translation project</a> are looking for volunteers.</p>
<p>Other projects that are in development or will commence in the near future include:</p>
<ul>
<li>A Burmese (my_MM) locale for the <a href="http://www.unicode.org/cldr/">Common Locale Data Repository</a>.</li>
<li>A Burmese collation algorithm for <a href="http://www.icu-project.org/">ICU</a>.</li>
<li>A Burmese line breaking algorithm for <a href="http://www.icu-project.org/">ICU</a></li>
</ul>
<p>All these will be based on the Unicode 5.1 Myanmar block.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2008/05/19/burmese-openoffice/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Firefox and web email services: Hotmail</title>
		<link>http://blogs.openroad.net.au/2007/12/12/firefox-and-web-email-services-hotmail/</link>
		<comments>http://blogs.openroad.net.au/2007/12/12/firefox-and-web-email-services-hotmail/#comments</comments>
		<pubDate>Wed, 12 Dec 2007 07:09:02 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Firefox]]></category>

		<category><![CDATA[MPAS]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/12/12/firefox-and-web-email-services-hotmail/</guid>
		<description><![CDATA[In the first and second parts I gave an example of using stylish to control font display for minority languages within Gmail and Yahoo. In this post I will quickly look at Hotmail.
]]></description>
			<content:encoded><![CDATA[<p>In the <a href="http://blogs.openroad.net.au/2007/05/31/firefox-and-web-email-services/">first</a> and <a href="http://blogs.openroad.net.au/2007/11/21/firefox-and-web-email-services-yahoo/">second</a> parts I gave an example of using stylish to control font display for minority languages within Gmail and Yahoo. In this post I will quickly look at Hotmail.</p>
<p> <a href="http://blogs.openroad.net.au/2007/12/12/firefox-and-web-email-services-hotmail/#more-30" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/12/12/firefox-and-web-email-services-hotmail/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Firefox and web email services: Yahoo</title>
		<link>http://blogs.openroad.net.au/2007/11/21/firefox-and-web-email-services-yahoo/</link>
		<comments>http://blogs.openroad.net.au/2007/11/21/firefox-and-web-email-services-yahoo/#comments</comments>
		<pubDate>Wed, 21 Nov 2007 02:01:35 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Firefox]]></category>

		<category><![CDATA[MPAS]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/11/21/firefox-and-web-email-services-yahoo/</guid>
		<description><![CDATA[In the first part I gave an example of using stylish to control font display for minority languages within Gmail. In this post II&#8217;ll quickly look at Yahoo&#8217;s new email web interface. These CSS rules do not apply to the classic mail UI.
]]></description>
			<content:encoded><![CDATA[<p>In the <a href="http://blogs.openroad.net.au/2007/05/31/firefox-and-web-email-services/">first part</a> I gave an example of using <a href="https://addons.mozilla.org/en-US/firefox/addon/2108">stylish</a> to control font display for minority languages within Gmail. In this post II&#8217;ll quickly look at Yahoo&#8217;s new email web interface. These CSS rules do not apply to the classic mail <abbr title="User Interface">UI</abbr>.</p>
<p> <a href="http://blogs.openroad.net.au/2007/11/21/firefox-and-web-email-services-yahoo/#more-29" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/11/21/firefox-and-web-email-services-yahoo/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Latin as a complex script</title>
		<link>http://blogs.openroad.net.au/2007/10/31/complex_latin/</link>
		<comments>http://blogs.openroad.net.au/2007/10/31/complex_latin/#comments</comments>
		<pubDate>Tue, 30 Oct 2007 23:15:07 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Web i18n]]></category>

		<category><![CDATA[MPAS]]></category>

		<category><![CDATA[Language enablement]]></category>

		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/10/31/complex_latin/</guid>
		<description><![CDATA[Current font technologies and font rendering systems make a distinction between writing scripts that require complex rendering and those scripts that do not. In most cases Latin is treated as a non-complex script. For a range of African and South East Asian languages that use the Latin script, the Latin script needs to be treated [...]]]></description>
			<content:encoded><![CDATA[<p>Current font technologies and font rendering systems make a distinction between writing scripts that require complex rendering and those scripts that do not. In most cases Latin is treated as a non-complex script. For a range of African and South East Asian languages that use the Latin script, the Latin script needs to be treated as a complex script.</p>
<p> <a href="http://blogs.openroad.net.au/2007/10/31/complex_latin/#more-3" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/10/31/complex_latin/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Language specific styling</title>
		<link>http://blogs.openroad.net.au/2007/10/23/language_styling/</link>
		<comments>http://blogs.openroad.net.au/2007/10/23/language_styling/#comments</comments>
		<pubDate>Tue, 23 Oct 2007 04:48:45 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Web i18n]]></category>

		<category><![CDATA[Typography]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/10/23/language_styling/</guid>
		<description><![CDATA[The W3C website has an article on using CSS 2.1 selectors to apply language specific styling based on the language of an element. This is quite an effective tool for developing websites with multilingual content.
The key drawback to using language specific styling is Internet Explorer&#8217;s limited support for CSS 2.1 selectors. Although there are strategies [...]]]></description>
			<content:encoded><![CDATA[<p>The W3C website has an article on using CSS 2.1 selectors to apply <a href="http://www.w3.org/International/questions/qa-css-lang">language specific styling</a> based on the language of an element. This is quite an effective tool for developing websites with multilingual content.</p>
<p>The key drawback to using language specific styling is Internet Explorer&#8217;s limited support for CSS 2.1 selectors. Although there are strategies to address Internet Explorer&#8217;s deficiencies. </p>
<p><a href="http://www.vicnet.net.au/">Vicnet&#8217;s</a> internal projects may involve one language, five languages or seventy languages. Language specific styling is a useful way to address a range of design issues within websites with multilingual content. this article will provide a brief look at the some of the strategies and techniques we use within our projects.</p>
<p> <a href="http://blogs.openroad.net.au/2007/10/23/language_styling/#more-25" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/10/23/language_styling/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Intersections in cyberspace 2: Centrelink and DIAC multilingual content</title>
		<link>http://blogs.openroad.net.au/2007/09/28/intersections-in-cyberspace-2-centrelink-and-diac-multilingual-content/</link>
		<comments>http://blogs.openroad.net.au/2007/09/28/intersections-in-cyberspace-2-centrelink-and-diac-multilingual-content/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 07:29:10 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Accessibility]]></category>

		<category><![CDATA[Web i18n]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/09/28/intersections-in-cyberspace-2-centrelink-and-diac-multilingual-content/</guid>
		<description><![CDATA[In part 1 I indicated that I would discuss internationalization of Australian Government websites with respect to accessibility by referencing two particular federal government websites. In this article I&#8217;ll be discussing the Centrelink and DIAC websites. 
]]></description>
			<content:encoded><![CDATA[<p>In <a href="/2007/07/14/intersections-in-cyberspace-internationalisation-accessibility-and-community-languages/">part 1</a> I indicated that I would discuss internationalization of Australian Government websites with respect to accessibility by referencing two particular federal government websites. In this article I&#8217;ll be discussing the <a href="http://www.centrelink.gov.au/">Centrelink</a> and <a href="http://www.immi.gov.au/"><abbr title="Department of Immigration and Citizenship">DIAC</abbr></a> websites. </p>
<p> <a href="http://blogs.openroad.net.au/2007/09/28/intersections-in-cyberspace-2-centrelink-and-diac-multilingual-content/#more-20" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/09/28/intersections-in-cyberspace-2-centrelink-and-diac-multilingual-content/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Community Languages Online</title>
		<link>http://blogs.openroad.net.au/2007/09/21/community-languages-online/</link>
		<comments>http://blogs.openroad.net.au/2007/09/21/community-languages-online/#comments</comments>
		<pubDate>Thu, 20 Sep 2007 22:37:57 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/09/21/community-languages-online/</guid>
		<description><![CDATA[The Community Languages Online report has been published on the eGovernment Resource Centre.
The report explores current practice and future directions of multilingual information on Victorian Government websites. It details findings and recommendations from research into how multilingual web-based government information can be created and used in the best way for culturally and linguistically diverse (CALD) [...]]]></description>
			<content:encoded><![CDATA[<p>The <cite><a href="http://www.egov.vic.gov.au/index.php?env=-innews/detail:m2807-1-1-8-s-0:n-1452-1-0">Community Languages Online</a></cite> report has been published on the <a href="http://www.egov.vic.gov.au/">eGovernment Resource Centre</a>.</p>
<p>The report explores current practice and future directions of multilingual information on Victorian Government websites. It details findings and recommendations from research into how multilingual web-based government information can be created and used in the best way for culturally and linguistically diverse (CALD) communities.</p>
<p>This report was produced for the former <a href="http://www.dvc.vic.gov.au/">Department for Victorian Communities</a> (now part of the Department of Planning and Community Development) by <a href="http://www.vicnet.net.au/">Vicnet</a>, a division of the <a href="http://www.slv.vic.gov.au/">State Library of Victoria</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/09/21/community-languages-online/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Intersections in cyberspace: internationalisation, accessibility and community languages</title>
		<link>http://blogs.openroad.net.au/2007/07/14/intersections-in-cyberspace-internationalisation-accessibility-and-community-languages/</link>
		<comments>http://blogs.openroad.net.au/2007/07/14/intersections-in-cyberspace-internationalisation-accessibility-and-community-languages/#comments</comments>
		<pubDate>Fri, 13 Jul 2007 14:53:04 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Accessibility]]></category>

		<category><![CDATA[Web i18n]]></category>

		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/07/14/intersections-in-cyberspace-internationalisation-accessibility-and-community-languages/</guid>
		<description><![CDATA[In the aftermath of the Community Languages Online report I&#8217;ve had time to start teasing out my thoughts on web internationalisation and accessibility as it applies to government information in community languages.
Web accessibility is well entrenched in federal and state governments&#8217; web standards in Australia. Generally web developers understand the need for web accessibility. Government [...]]]></description>
			<content:encoded><![CDATA[<p>In the aftermath of the <em><a href="http://www.egov.vic.gov.au/index.php?env=-innews/detail:m2807-1-1-8-s-0:n-1452-1-0">Community Languages Online</a></em> report I&#8217;ve had time to start teasing out my thoughts on web internationalisation and accessibility as it applies to government information in community languages.</p>
<p>Web accessibility is well entrenched in federal and state governments&#8217; web standards in Australia. Generally web developers understand the need for web accessibility. Government departments and agencies require web accessibility and will make the effort to get their websites to comply with accessibility standards.</p>
<p>This seems to work smoothly in monolingual environments, but there is a fracture point. Looking at Australian government websites, it becomes apparent that key aspects of web accessibility (and its relationship with web internationalisation) is only superficially understood.</p>
<p>In a future post I&#8217;ll discuss two particular federal government websites. For the moment I&#8217;ll concentrate on my understanding of web accessibility as it applies to content in community languages.</p>
<p> <a href="http://blogs.openroad.net.au/2007/07/14/intersections-in-cyberspace-internationalisation-accessibility-and-community-languages/#more-21" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/07/14/intersections-in-cyberspace-internationalisation-accessibility-and-community-languages/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Looking forward &#8230; SE Asian scripts support</title>
		<link>http://blogs.openroad.net.au/2007/06/08/looking-forward-se-asian-scripts-support/</link>
		<comments>http://blogs.openroad.net.au/2007/06/08/looking-forward-se-asian-scripts-support/#comments</comments>
		<pubDate>Fri, 08 Jun 2007 07:35:08 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Scripts]]></category>

		<category><![CDATA[Language enablement]]></category>

		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/06/08/looking-forward-se-asian-scripts-support/</guid>
		<description><![CDATA[A number of changes to the Myanmar script and proposed support for additional South east Asian support are in the ISO/IEC 10646 and Unicode pipelines over the next year or two.
Andrew West provides a very good summary of what will be in Unicode 5.1 in his post What&#8217;s new in Unicode 5.1 ?.
]]></description>
			<content:encoded><![CDATA[<p>A number of changes to the Myanmar script and proposed support for additional South east Asian support are in the ISO/IEC 10646 and Unicode pipelines over the next year or two.</p>
<p>Andrew West provides a very good summary of what will be in Unicode 5.1 in his post <cite><a href="http://babelstone.blogspot.com/2007/06/whats-new-in-unicode-51.html">What&#8217;s new in Unicode 5.1 ?</a></cite>.</p>
<p> <a href="http://blogs.openroad.net.au/2007/06/08/looking-forward-se-asian-scripts-support/#more-18" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/06/08/looking-forward-se-asian-scripts-support/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Myanmar script and Unicode</title>
		<link>http://blogs.openroad.net.au/2007/06/03/the-myanmar-script-and-unicode/</link>
		<comments>http://blogs.openroad.net.au/2007/06/03/the-myanmar-script-and-unicode/#comments</comments>
		<pubDate>Sun, 03 Jun 2007 05:53:49 +0000</pubDate>
		<dc:creator>Andrew Cunningham</dc:creator>
		
		<category><![CDATA[Languages]]></category>

		<guid isPermaLink="false">http://blogs.openroad.net.au/2007/06/03/the-myanmar-script-and-unicode/</guid>
		<description><![CDATA[I&#8217;ve been looking into Unicode support for the Myanmar Script. A few local projects require Unicode support for Myanmar (Burmese), Mon and S&#8217;gaw Karen. The existing Unicode Myanmar block only supports Myanmar (Burmese). Unicode 5.1 will make changes to the existing Myanmar block and add additional characters for Mon and S&#8217;gaw Karen. Proposals have been [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been looking into Unicode support for the Myanmar Script. A few local projects require Unicode support for Myanmar (Burmese), Mon and S&#8217;gaw Karen. The existing Unicode Myanmar block only supports Myanmar (Burmese). Unicode 5.1 will make changes to the existing Myanmar block and add additional characters for Mon and S&#8217;gaw Karen. Proposals have been submitted to add additional characters to support other ethnic minority languages of the Myanmar Union.</p>
<p>The following notes attempt to summarize current status of Unicode support for the Myanmar script.</p>
<p> <a href="http://blogs.openroad.net.au/2007/06/03/the-myanmar-script-and-unicode/#more-11" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.openroad.net.au/2007/06/03/the-myanmar-script-and-unicode/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
