2015-03-02 16:48 GMT+01:00 Rafael Ferreira :
> It looks to me that both 1 and 3 will represent a bug in Danish
> localization. Forcing 24-hour (option 1) will show a weird 12-hour
> button that returns 24-hour, while using 12-hour (option 3) will show
> a 12-hour clock that doesn't exists in Danish
Well, I think the best option is number 2. It produces things that
are correct in Danish (05:00 and 17:00 can both be "5 o'clock" in
normal non-computer speech) which, although quite useless due to the
ambiguity, is not a problem because no Danish user should/would be
using 12-hour clock setting a
2015-03-02 8:49 GMT-03:00 Alexandre Franke :
> On Mon, Mar 2, 2015 at 12:08 PM, wrote:
>> For Danish, ther is no 12-hour format. The best is then to leave the
>> specification blank.
>
> This is a terrible suggestion. You should never leave a string blank.
> If you intend to use the same as the
On Mon, Mar 02, 2015 at 12:49:37PM +0100, Alexandre Franke wrote:
> On Mon, Mar 2, 2015 at 12:08 PM, wrote:
> > For Danish, ther is no 12-hour format. The best is then to leave the
> > specification blank.
>
> This is a terrible suggestion. You should never leave a string blank.
> If you intend
On Sun, Mar 1, 2015 at 9:56 PM, Alexandre Franke
wrote:
> Hi,
>
> On Sat, Feb 28, 2015 at 8:05 PM, Ask Hjorth Larsen
> wrote:
>> 1) Force the user to use 24-hour clock by simply translating it to "%H:%M",
>> or
>> 2) use the imprecise "%l:%M", or
>> 3) retain the alien "%l:%M %p"?
>
> In any
On Mon, Mar 2, 2015 at 12:08 PM, wrote:
> For Danish, ther is no 12-hour format. The best is then to leave the
> specification blank.
This is a terrible suggestion. You should never leave a string blank.
If you intend to use the same as the original version, you should copy
it.
> Alternatively
For Danish, ther is no 12-hour format. The best is then to leave the
specification blank.
Alternatively you can make the 12-hour format the same as the 24-hour format.
keld
On Sun, Mar 01, 2015 at 03:07:26PM +0100, Ask Hjorth Larsen wrote:
> Hello Hannie
>
> I should clarify: This is when the
Hi Ask,
If the comment explicitly says 12-hour clock, I think you should
translate it as 12-hour+am/pm (%p).
Hannie
Op 01-03-15 om 15:07 schreef Ask Hjorth Larsen:
Hello Hannie
I should clarify: This is when the translator comment says "12-hour
clock format" and there's another string called
2015-02-28 16:05 GMT-03:00 Ask Hjorth Larsen :
>
> 1) Force the user to use 24-hour clock by simply translating it to "%H:%M",
> or
> 2) use the imprecise "%l:%M", or
> 3) retain the alien "%l:%M %p"?
>
Brazilian Portuguese team co-coordinator here. In Brazil we know the
12-hour clock due to s
Hi,
On Sat, Feb 28, 2015 at 8:05 PM, Ask Hjorth Larsen wrote:
> 1) Force the user to use 24-hour clock by simply translating it to "%H:%M",
> or
> 2) use the imprecise "%l:%M", or
> 3) retain the alien "%l:%M %p"?
In any case it shouldn't be 1. If someone requests time in 12hrs
format and se
Hello Hannie
I should clarify: This is when the translator comment says "12-hour
clock format" and there's another string called "24-hour clock
format". I have to translate both, and I leave the 24-hour clock
format unchanged. The locale settings should choose the 24-hour clock
format presumably
We, the Dutch translation team, use the 24-hour clock most of the time,
since this is custom in our country.
Hannie
Op 28-02-15 om 20:05 schreef Ask Hjorth Larsen:
Hello
In many languages including Danish, "am" and "pm" ("%p" in strftime)
do not exist. When using the 12-hour clock one would s
Hello
In many languages including Danish, "am" and "pm" ("%p" in strftime)
do not exist. When using the 12-hour clock one would simply say e.g.
"11:32" which is of course ambiguous. On a computer one would use the
24-hour clock to simply avoid this ambiguity.
However we still have to provide a
13 matches
Mail list logo
