On Sunday, 19 May 2019 at 12:24:28 UTC, Patrick Schluter wrote:
> On Saturday, 18 May 2019 at 21:05:13 UTC, Les De Ridder wrote:
>> On Saturday, 18 May 2019 at 20:34:33 UTC, Patrick Schluter wrote:
>>> * hurrah for French keyboard which has a rarely used µ key, but none for Ç a frequent character of the language.
>>
>> <Caps Lock><key marked with '9' on the number row><Caps Lock>
>
> That's the lowercase ç. The uppercase Ç is not directly composable,

No, note that I said <Caps Lock> and not <Shift>. Using <Caps Lock> it
outputs a 'Ç' for me (at least on X11 with the French layout).

>
> There are 2 other characters that are not available on the french keyboard: œ and Œ. Quite annoying if you sell beef (bœuf) and eggs (œufs) in the towns of Œutrange or Œting.

It seems those are indeed not on the French layout at all. Might I
suggest using the Belgian layout? It is AZERTY too and has both 'œ'
and 'Œ'.

On Thursday, 16 May 2019 at 15:52:05 UTC, Steven Schveighoffer wrote:
> On 5/16/19 4:27 PM, Vladimir Panteleev wrote:
>> On Thursday, 16 May 2019 at 15:19:03 UTC, Alex wrote:
>
>>> What's an hnsec anyways?
>> 
>> Hecto-nano-second, the smallest representable unit of time in SysTime and Duration.
>
> The output shouldn't involve the inner workings of the type. It should be changed to say 10 ns.
>
> -Steve

It's 100ns. 10ns = 1dans = 1 deka-nano-second.
deka = 10, hecto = 100 [1]

[1] https://www.nist.gov/pml/weights-and-measures/metric-si-prefixes

On Tuesday, 21 May 2019 at 02:12:10 UTC, Les De Ridder wrote:
> On Sunday, 19 May 2019 at 12:24:28 UTC, Patrick Schluter wrote:
>> On Saturday, 18 May 2019 at 21:05:13 UTC, Les De Ridder wrote:
>>> On Saturday, 18 May 2019 at 20:34:33 UTC, Patrick Schluter wrote:
>>>> * hurrah for French keyboard which has a rarely used µ key, but none for Ç a frequent character of the language.
>>>
>>> <Caps Lock><key marked with '9' on the number row><Caps Lock>
>>
>> That's the lowercase ç. The uppercase Ç is not directly composable,
>
> No, note that I said <Caps Lock> and not <Shift>. Using <Caps Lock> it
> outputs a 'Ç' for me (at least on X11 with the French layout).

Does not work on Windows. <Caps lock> and it gives 9. I tested also on my Linux Mint box and it output lowercase ç with <Caps lock>.

>
>>
>> There are 2 other characters that are not available on the french keyboard: œ and Œ. Quite annoying if you sell beef (bœuf) and eggs (œufs) in the towns of Œutrange or Œting.
>
> It seems those are indeed not on the French layout at all. Might I
> suggest using the Belgian layout? It is AZERTY too and has both 'œ'
> and 'Œ'.

No, it hasn't.
I indeed prefer the Belgian keyboard. It has more composable deadkey characters accents, tildas. Brackets [{]} and other programming characters < > | etc, are better placed than on the French keyboard.
Btw æ and Æ are missing also, but there it's not very important as there are really only very few words in French that use them ex-æquo, curriculum vitæ, et cætera

On Friday, 17 May 2019 at 18:02:04 UTC, kdevel wrote:
> On Thursday, 16 May 2019 at 20:31:23 UTC, Vladimir Panteleev wrote:
>> On Thursday, 16 May 2019 at 20:17:37 UTC, Steven Schveighoffer
>
> [...]
>
>>> hnsecs is more confusing than nanoseconds. People know what a nanosecond is, a hecto-nano-second is not as familiar a term.
>>
>> Agreed, which is why Duration.toString shouldn't be used to present durations to users.
>>
>> Developers, however, are expected to know what a hectonanosecond is, same as with all the other technical terms.
>
> "hectonanosecond" looks like an illegal combination of SI prefixes [1]. I recommend changing the meaning of hnsecs to "[one] hundred nanoseconds".
>
> [1] "Prefixes may not be used in combination."
>     https://en.wikipedia.org/wiki/Metric_prefix

Exactly it really does not exist. Just try to search it on net. No one know what is it. Only few people from D world use it. Every time I need to work with D and time it takes hours to find out what hnsecs is.

>> Why not simply 17.5531 ms ("%.4f ms") to get rid of the non-ASCII µ prefix?
> fwiw I like this solution for the output. It is very clear to me.
+1
and without space 17.5531ms