From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Feedback on NI Community

cancel
Showing results for 
Search instead for 
Did you mean: 

Localization of (forum) maintenance announcements

Hi,

 

it's fine you announce maintenance intervals with some advance. It's also fine you localize that message according to user regional settings:

It would be even better when you would also localize the timestamps with respect to user's regional settings. Right now it some heavy kind of "Denglisch" (meaning a wild mix of English and German) as we say in Germany. It's quite hard to think about AM/PM and CST times here in the center of Europe…

 

Asking as a programmer: what is "18:00 PM" exactly? Do you use 24h format or do you use 12 hour format with AM/PM? Does CST only apply to Sunday or also to Friday timestamp?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 1 of 11
(2,177 Views)

Hi @GerdW 

 

That is good feedback. I will pass it along to the team that is doing that maintenance, which is not specific to NI Community. When I post NI Community planned maintenance, I always work to include both CST/CDT and UTC.

 

Best,

Mark

Community Manager
NI Community
0 Kudos
Message 2 of 11
(2,171 Views)

For comparison, here's the current English (US) version:

 

altenbach_0-1650564873377.png

 

0 Kudos
Message 3 of 11
(2,147 Views)

Hi Mark,

 

the next maintenance the same localisation problem...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 4 of 11
(2,028 Views)

And again we have a forum maintenance and still get the same mix of German text with English timestamps. And those timestamps also still use some CDT + AM/PM format totally unrelated to my CEST timezone…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 5 of 11
(1,929 Views)

Next forum maintenance, still the same bogus timestamps in the message!

 

Why do i have to think about CST times in a localised German message? Added bonus: we still have to count for DST in Europe...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 11
(1,810 Views)

Hi,

 

while we had UTC times in announcements the last time you now forgot about them again:

Still a mix of German and English, still just US timezones, now even with wrong dates/weekdays...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 7 of 11
(262 Views)

The same in Italian localization:

Screenshot 2024-03-20 12.10.26.png

 

And I wonder why 05:00 AM in Germany and 06:00 in Italy 🙄



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 8 of 11
(251 Views)

Hi Roberto,

 


@RobertoBozzolo wrote:

And I wonder why 05:00 AM in Germany and 06:00 in Italy 🙄


Because someone corrected the whole message as it now correctly claims Tuesday/Wednesday instead of Monday/Tuesday - and so added one more hour for the update time frame…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 9 of 11
(240 Views)

Time should not be so difficult. 

 

Sol is apparently overhead nearby thusly! 

12ish should not be a problem! Screw DST!

 

 

(Yes, Terra is spinning fast, probably a major slipfault earthquake is due! Ask any icedancer about rotation and inertia)


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 11
(81 Views)