Tobias Rapp

> There doesn't seem to be such information in Broadcast Wave File. So I'm not sure there's an existing standard for the values that are commonly found. The coding history...

> Is the `T=Deemphasis` a NOA specific thing? Basically yes. In BWF Coding History anything on a line after `T=` is free text, but NOA uses some sub-tagging for adding...

Stumbled over the missing implementation of `Option`, too. Unfortunately it cannot manually be implemented outside of Approx as `Option` is a foreign type, and `AbsDiffEq` is a foreign trait to...

For anyone interested in long path support: Stumbled over this recent [pull request for rustc](https://github.com/rust-lang/rust/pull/96737) which adds a similar manifest file to the rustc executable. It apparently works for the...

Sidenote: Maybe the definition could also be extended for FieldOrder values "1" and "6" to make it explicit that they shall be used when fields are stored separately - in...

There was agreement in the discussion at [vrecord/#170](https://github.com/amiaopensource/vrecord/issues/170#issuecomment-321668000) that the actual practice for field-order values in MOV is: * 9 → Interlaced field storage with _top field_ displayed first *...

It seems that tabular figures are available in version 4.0 of this font, which is great!

Noticed something similar. About half of the tested WinXP VMs are still reported as vulnerable by rdpscan after KB4500331 has been applied and the machine was restarted, but none of...