Re: Windows 10 datetime formats - I need help

2015-08-06 Thread Paul Hill
On 5 August 2015 at 22:19, Stephen Russell srussell...@gmail.com wrote:
 On Wed, Aug 5, 2015 at 3:06 PM, Paul Hill paulroberth...@gmail.com wrote:

 Hi All,

 I discovered this bug in C# but I suspect it will effect other
 languages. It looks like ADO is effected so could effect Fox.

 Windows 10 introduced changes to the following cultures:
 Finnish (Finland)
 Norwegian Bokmål (Norway)
 Norwegian Bokmål (Svalbard and Jan Mayen)
 Serbian (Cyrillic, Kosovo)
 Serbian (Latin, Montenegro)
 Serbian (Latin, Serbia)
 Serbian (Latin, Kosovo)

 The date separator for these cultures has changed to the same as the
 time separator.

 For example, in Windows 8 Norway used: 05.08.2015 20:53
 In Windows 10 it uses 05.08.2015 20.53

 Is this a .Net 4.6 issue?  Have seen a few OBTW for 4.6 over the past few
 weeks.

I don't think so.  I'm using 4.0.  Although I believe if you target
4.0 it will actually use 4.6.
I suspect if I made a custom locale for Windows 8 it would have the
same problems.

-- 
Paul

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CADwx0+LHRSi0zGgQCtQxUvis=xozvdsapenr2a93t9ozqzr...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Windows 10 datetime formats - I need help

2015-08-05 Thread Paul Hill
Hi All,

I discovered this bug in C# but I suspect it will effect other
languages. It looks like ADO is effected so could effect Fox.

Windows 10 introduced changes to the following cultures:
Finnish (Finland)
Norwegian Bokmål (Norway)
Norwegian Bokmål (Svalbard and Jan Mayen)
Serbian (Cyrillic, Kosovo)
Serbian (Latin, Montenegro)
Serbian (Latin, Serbia)
Serbian (Latin, Kosovo)

The date separator for these cultures has changed to the same as the
time separator.

For example, in Windows 8 Norway used: 05.08.2015 20:53
In Windows 10 it uses 05.08.2015 20.53

Notice the time.

The documentation for dot net Convert.ToDateTime() specifies If value
contains only a date and no time, this method assumes a time of
midnight.
https://msdn.microsoft.com/en-us/library/xhz1w05e(v=vs.110).aspx

This does *not* work for the cultures I listed.

Please do me a huge favour by upvoting the following:
https://connect.microsoft.com/VisualStudio/feedback/details/1621722/norwegian-culture-problem-date-parsing

-- 
Paul

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/cadwx0+lpwq1z3uraaajkwtzm0yzexzeqxasxkhf6ve14ubm...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: Windows 10 datetime formats - I need help

2015-08-05 Thread Stephen Russell
On Wed, Aug 5, 2015 at 3:06 PM, Paul Hill paulroberth...@gmail.com wrote:

 Hi All,

 I discovered this bug in C# but I suspect it will effect other
 languages. It looks like ADO is effected so could effect Fox.

 Windows 10 introduced changes to the following cultures:
 Finnish (Finland)
 Norwegian Bokmål (Norway)
 Norwegian Bokmål (Svalbard and Jan Mayen)
 Serbian (Cyrillic, Kosovo)
 Serbian (Latin, Montenegro)
 Serbian (Latin, Serbia)
 Serbian (Latin, Kosovo)

 The date separator for these cultures has changed to the same as the
 time separator.

 For example, in Windows 8 Norway used: 05.08.2015 20:53
 In Windows 10 it uses 05.08.2015 20.53

---


Is this a .Net 4.6 issue?  Have seen a few OBTW for 4.6 over the past few
weeks.





-- 
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN

901.246-0159 cell


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAJidMY+YAPLAU8yveX-ReQ0GsnY0BF_qNr8=d+dubccubf1...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.