<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mekhala browser, Moyura mail, KhmerOS</title>
	<atom:link href="http://blog.mozilla.com/gen/2009/04/15/mekhala-browser-moyura-mail-khmeros/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/gen/2009/04/15/mekhala-browser-moyura-mail-khmeros/</link>
	<description>Gen Kanai's Mozilla weblog</description>
	<lastBuildDate>Mon, 06 Feb 2012 17:29:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: keng</title>
		<link>http://blog.mozilla.com/gen/2009/04/15/mekhala-browser-moyura-mail-khmeros/comment-page-1/#comment-84539</link>
		<dc:creator>keng</dc:creator>
		<pubDate>Wed, 15 Apr 2009 21:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/gen/?p=299#comment-84539</guid>
		<description>@ac,

I think Khmer and Thai as well as, AFAIK, Gujarati are facing the same problem on text rendering, for example too small room for rendering thai characters in location bar.

To me, supporting those issues are neccessary, but nice to have, sometime. In trem of Thai, we focus on localise, make the more user related things done -- page&#039;s wordbreak/rendering, l10n -- first, get local people more familiar with it, then go with more tech related issues.

My point is the issue like separate branch and redesign dialog is needed as well, but it shouldn&#039;t drag the user related issue to be fixed, in term of Khmer, i guessed, everything is ready, just put all the Khmer L10n to mozilla to reduce new release catch-up efford for Khmer L10n team, then go for bigger issue, redesign.

Keng.</description>
		<content:encoded><![CDATA[<p>@ac,</p>
<p>I think Khmer and Thai as well as, AFAIK, Gujarati are facing the same problem on text rendering, for example too small room for rendering thai characters in location bar.</p>
<p>To me, supporting those issues are neccessary, but nice to have, sometime. In trem of Thai, we focus on localise, make the more user related things done &#8212; page&#8217;s wordbreak/rendering, l10n &#8212; first, get local people more familiar with it, then go with more tech related issues.</p>
<p>My point is the issue like separate branch and redesign dialog is needed as well, but it shouldn&#8217;t drag the user related issue to be fixed, in term of Khmer, i guessed, everything is ready, just put all the Khmer L10n to mozilla to reduce new release catch-up efford for Khmer L10n team, then go for bigger issue, redesign.</p>
<p>Keng.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gen Kanai</title>
		<link>http://blog.mozilla.com/gen/2009/04/15/mekhala-browser-moyura-mail-khmeros/comment-page-1/#comment-84525</link>
		<dc:creator>Gen Kanai</dc:creator>
		<pubDate>Wed, 15 Apr 2009 15:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/gen/?p=299#comment-84525</guid>
		<description>ac, I&#039;m not sure what screen sizes are normal in Cambodia.  I&#039;d imagine they&#039;d be similar to what is popular elsewhere?  

Regarding the size of Khmer text and compromises in UI, I&#039;m hoping we can look at the issues with fresh eyes as those bugs are quite old and try to find creative solutions. 

Realistically, the list of localizations for Firefox 3.5 is basically fixed, so any discussion of a Khmer Firefox would be for a post-3.5 release.</description>
		<content:encoded><![CDATA[<p>ac, I&#8217;m not sure what screen sizes are normal in Cambodia.  I&#8217;d imagine they&#8217;d be similar to what is popular elsewhere?  </p>
<p>Regarding the size of Khmer text and compromises in UI, I&#8217;m hoping we can look at the issues with fresh eyes as those bugs are quite old and try to find creative solutions. </p>
<p>Realistically, the list of localizations for Firefox 3.5 is basically fixed, so any discussion of a Khmer Firefox would be for a post-3.5 release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ac</title>
		<link>http://blog.mozilla.com/gen/2009/04/15/mekhala-browser-moyura-mail-khmeros/comment-page-1/#comment-84514</link>
		<dc:creator>ac</dc:creator>
		<pubDate>Wed, 15 Apr 2009 13:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/gen/?p=299#comment-84514</guid>
		<description>What size screens are normal in Cambodia these days?
Khmer text is taller than most other writing systems since it must provide room for multiple marks both above and below the letters.
It looks like a prior Khmer localization effort apparently failed because Mozilla UI leaders 
* weren&#039;t willing to accept a redesign for the dialogs (more tabs) so they could display tall Khmer text and still fit on an 800x600 screen common there at the time, and
* weren&#039;t willing to allow scrollbars to appear in dialogs if needed.  
(for example, bug 259228, bug 259959).   
With the popularity of netbooks, small screens are still likely to be a problem.
A separate branch with redesigned dialogs may still be necessary.</description>
		<content:encoded><![CDATA[<p>What size screens are normal in Cambodia these days?<br />
Khmer text is taller than most other writing systems since it must provide room for multiple marks both above and below the letters.<br />
It looks like a prior Khmer localization effort apparently failed because Mozilla UI leaders<br />
* weren&#8217;t willing to accept a redesign for the dialogs (more tabs) so they could display tall Khmer text and still fit on an 800&#215;600 screen common there at the time, and<br />
* weren&#8217;t willing to allow scrollbars to appear in dialogs if needed.<br />
(for example, bug 259228, bug 259959).<br />
With the popularity of netbooks, small screens are still likely to be a problem.<br />
A separate branch with redesigned dialogs may still be necessary.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

