This project is read-only.


Force content importer culture to en-US


<p>As proposed in Discussions, this will see the content importer forced to use en-US culture when importing. This will affect importing numerical values, as everyone will have to use a period &quot;.&quot; as the decimal separator, no matter what the user&#39;s system culture is. (Commas will not work at all)</p>
Closed Dec 10, 2011 at 2:16 AM by
Assuming this is fixed so that we can release 1.3 soon.


Qbus wrote Oct 20, 2011 at 3:14 PM

Yes we need this. I guess most, if not all, .NET developer are used to use en-US culture when coding, no matter their own culture.

Chr0n1x wrote Nov 20, 2011 at 2:54 PM

Added to v1.3 release, set to active and myself. Will add in with other fixes this week.

Chr0n1x wrote Nov 20, 2011 at 3:07 PM

Fixed in rev 71043. Can you verify that everything works as you want it? Then I can close this.