Hirundo opened the ticket and wrote:

Patched against r22765

Attached is a series of patches that does the following in order:
- Change current NewGRF date string codes (82, 83) to interpret their argument as unsigned. Although the sign is not explicitly mentioned in the specs, this IMO qualifies as a bug fix since base-1920 dates are unsigned everywhere else.
- Fix: Let NewGRF string code 83 use the 'short' instead of 'tiny' date format to comply with specs.
- Rename NewGRF date string codes to clarify the size of their argument
- Add 2 NewGRF 9A string codes (16 and 17) that are equivalent to the existing 82 and 83, but with a dword-sized base-0 date as argument
- Add 2 NewGRF 9A string codes (18 and 19) that pop a signed dword off the stack and print it as 'power' resp. 'force'. This intended for use in the vehicle buy menu, so (combined with the 'push word' string code) you can display power or force in correct units in the NewGRF-supplied additional text.

Attachments

• 0_unsigneddate.diff (0.74 KiB)
• 1_shortdate.diff (0.43 KiB)
• 2_renamedate.diff (5.17 KiB)
• 3_date_codes.diff (2.65 KiB)
• 4_force_power_codes.diff (2.07 KiB)
• total.diff (6.65 KiB)

Reported version: trunk
Operating system: All

This issue was imported from FlySpray: https://bugs.openttd.org/task/4738