Territory_ConvertTimeFormats

You only need Arabic font support for Arabic language support. The Hijri Calendar is not dependent on any particular script. e.g. The first three months, roughly mapping to August-October, are Muharram, Safar and Rabi’al-Awwal. No Arabic necessary.

What a tangled Web we weave when seek we answers on the ROOL forum.

Something sorely missing from RISC OS is the simple ability to output and parse various standard and commonplace date strings that can be found on-line. Like those used in cookies, 8601 (old and new), and various RFC formats (for usenet headers, email headers, and so on).

A few years ago I wrote some of my own code to handle RFC 3339, and once it was working I decided that it would be useful to add support directly to the Territory Manager. My thought process went something like this:

Oh, it’s a wodge of assembly. Never mind then.

The problem with any international standard related to UTC is that RISC OS doesn’t actually support UTC, it only pretends to (see leap seconds for the missing bit).

it’s a wodge of assembly. Never mind then.

That’s a shame but 3339 is trivial and is one of the few formats that can be implemented inside TerritoryManager as there’s no locale-specific elements in it.

Anything with month names has to be in the individual Territory modules, although why you’d want a German machine to not parse “25 Dec 2023” is difficult to justify – perhaps the Territory should have first go, but TerritoryManager provides a default multilingual result if the configured Territory can’t translate. Reduces the burden on Territories and provides a baseline quality of service.

Anything with month names has to be in the individual Territory modules

Not necessarily. RFC822 specifies that the day and month names will be in English. So it only needs one parser to handle this.

Then it can be done once correctly, like understanding the difference between the timezone offset of +0000 and -0000. ;)

Not necessarily

Rephrased: In those cases that contain a localised (or undefined) month, it seems strange that TerritoryManager requires the one Territory to recognise all possible inputs.

I was suggesting a multilingual fallback would be advantageous.