<?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: Need Feedback From Arabic, Chinese And Several Other Cultures</title>
	<atom:link href="http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/</link>
	<description>An open-source JavaScript Date Library</description>
	<lastBuildDate>Tue, 20 Jul 2010 22:24:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: JRK</title>
		<link>http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/comment-page-1/#comment-59</link>
		<dc:creator>JRK</dc:creator>
		<pubDate>Mon, 03 Aug 2009 12:57:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/#comment-59</guid>
		<description>I don&#039;t know ANYTHING about Arabic, but while trying to localize an app to ar-AE, it can&#039;t seem to handle:

Date.parse(&#039;07:30 ص&#039;);

US-equivalent:

Date.parse(&#039;7:30 AM&#039;);</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know ANYTHING about Arabic, but while trying to localize an app to ar-AE, it can&#8217;t seem to handle:</p>
<p>Date.parse(&#8217;07:30 ص&#8217;);</p>
<p>US-equivalent:</p>
<p>Date.parse(&#8217;7:30 AM&#8217;);</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dietmar</title>
		<link>http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/comment-page-1/#comment-58</link>
		<dc:creator>Dietmar</dc:creator>
		<pubDate>Wed, 13 May 2009 15:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/#comment-58</guid>
		<description>Hi,

I have tried a couple of nationalizations and found only the english to be working properly. I specifically checked the German and French month names and came to the following conclusions:

1. If there are accented names (e.g. German &quot;März&quot; or French &quot;Février&quot;), these will not be recognized.

2. Even if a month name is recognized, it may not always deliver the correct date. E.g. try &quot;Oktober&quot; or &quot;Dezember&quot; in the German version, it will result in the current month. The same seems to be the case for any month name of the french translation.

3. The French regex patterns are crap as they always require the abbreviation period, even if the long name of a month is given. (E.g. &quot;Janvier&quot; does not work, but &quot;Janv.ier&quot; does.)

The last issue may be solved easily by altering the patterns. I cannot handle, however, the first two. Does anyone have any suggestions on that?

Best regards,
Dietmar.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have tried a couple of nationalizations and found only the english to be working properly. I specifically checked the German and French month names and came to the following conclusions:</p>
<p>1. If there are accented names (e.g. German &#8220;März&#8221; or French &#8220;Février&#8221;), these will not be recognized.</p>
<p>2. Even if a month name is recognized, it may not always deliver the correct date. E.g. try &#8220;Oktober&#8221; or &#8220;Dezember&#8221; in the German version, it will result in the current month. The same seems to be the case for any month name of the french translation.</p>
<p>3. The French regex patterns are crap as they always require the abbreviation period, even if the long name of a month is given. (E.g. &#8220;Janvier&#8221; does not work, but &#8220;Janv.ier&#8221; does.)</p>
<p>The last issue may be solved easily by altering the patterns. I cannot handle, however, the first two. Does anyone have any suggestions on that?</p>
<p>Best regards,<br />
Dietmar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: geoffrey.mcgill</title>
		<link>http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/comment-page-1/#comment-57</link>
		<dc:creator>geoffrey.mcgill</dc:creator>
		<pubDate>Wed, 26 Mar 2008 05:59:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/#comment-57</guid>
		<description>@Matteo - The strings used by the Parser for pattern matching (i.e. &quot;next&quot;, &quot;previous&quot;) are customizable by editing values within the regexPatterns node of the CultureInfo file.

The string &quot;next&quot; is located within the &quot;future&quot; pattern.

The string values &quot;previous&quot; and &quot;next&quot; are located within the &quot;past&quot; pattern.

Once updated the Parser will correctly parse both “prossimo sabato” and “sabato prossimo”.

Any help translating the strings within the CultureInfo files would be appreciated. Instructions for translating are provided within each culture-specific file located in /trunk/src/globalization/[culture].js

Several CultureInfo files have been translated by the community with download to each available in the forums (http://www.datejs.com/forums/).

I hope this helps answer your question.</description>
		<content:encoded><![CDATA[<p>@Matteo &#8211; The strings used by the Parser for pattern matching (i.e. &#8220;next&#8221;, &#8220;previous&#8221;) are customizable by editing values within the regexPatterns node of the CultureInfo file.</p>
<p>The string &#8220;next&#8221; is located within the &#8220;future&#8221; pattern.</p>
<p>The string values &#8220;previous&#8221; and &#8220;next&#8221; are located within the &#8220;past&#8221; pattern.</p>
<p>Once updated the Parser will correctly parse both “prossimo sabato” and “sabato prossimo”.</p>
<p>Any help translating the strings within the CultureInfo files would be appreciated. Instructions for translating are provided within each culture-specific file located in /trunk/src/globalization/[culture].js</p>
<p>Several CultureInfo files have been translated by the community with download to each available in the forums (<a href="http://www.datejs.com/forums/" rel="nofollow">http://www.datejs.com/forums/</a>).</p>
<p>I hope this helps answer your question.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matteo</title>
		<link>http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/comment-page-1/#comment-56</link>
		<dc:creator>Matteo</dc:creator>
		<pubDate>Fri, 29 Feb 2008 12:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.datejs.com/2008/02/10/need-feedback-from-arabic-chinese-and-several-other-cultures/#comment-56</guid>
		<description>About cultures I have a doubt regarding the Italian one.
I see that for, i.e., &quot;next saturday&quot; I would have to write &quot;next sabato&quot;. But in Italian it does not mean anything! I would have written &quot;sabato prossimo&quot; or &quot;prossimo sabato&quot;. Should &quot;next&quot; be reg-ex-ed using &quot;prossimo&quot; instead of &quot;next&quot;? Same thing holds for other &quot;relative&quot; dates (previous, last, etc...).

Thank you!</description>
		<content:encoded><![CDATA[<p>About cultures I have a doubt regarding the Italian one.<br />
I see that for, i.e., &#8220;next saturday&#8221; I would have to write &#8220;next sabato&#8221;. But in Italian it does not mean anything! I would have written &#8220;sabato prossimo&#8221; or &#8220;prossimo sabato&#8221;. Should &#8220;next&#8221; be reg-ex-ed using &#8220;prossimo&#8221; instead of &#8220;next&#8221;? Same thing holds for other &#8220;relative&#8221; dates (previous, last, etc&#8230;).</p>
<p>Thank you!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
