<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 14, 2015 at 7:36 AM, Eike Hein <span dir="ltr"><<a href="mailto:hein@kde.org" target="_blank">hein@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":aj" class="a3s" style="overflow:hidden">What's gone relative to the old KLocale system is that<br>
KLocale allowed you to essentially create a custom locale<br>
with custom values for time format, while the new system<br>
requires you to set Time to, say, "Germany" if you want a<br>
24 clock, which means you need to know which locale has<br>
the format you want. Which is fairly clumsy.</div></blockquote></div><br>Were you involved in this decision? Was the comment that I referred to earlier</div><div class="gmail_extra">in the thread about this being fixed in the May, 2015 timeframe incorrect?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Regarding setting your locale to "Germany" for 24 time? Correct me if I am mistaken</div><div class="gmail_extra">but that also changes currency to the Euro. If that is the case, as a solution it's not</div><div class="gmail_extra">"fairly clumsy" it's just ridiculous. How anyone could consider this is solution is beyond me.</div><div class="gmail_extra">It solves one issue and creates many more. Now the currency, date, etc. is in the wrong </div><div class="gmail_extra">format. It's just clueless.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>