CI: Add validation

[andrewbird]

No description provided.

[andrewbird]

@fritzmueller @PerditionC I fixed up the current tables to pass validation. I'd appreciate it if you could review the Country changes especially the last, Montenegro, as I had to make most of that up. Ooh, they're using the Euro without permission - nice!

[PerditionC]

I will try looking later this evening, if not it won't be until Friday that I have a chance again. I have some improvements to the source to minimize mistakes (850 vs 858 type) and improve readability via some additional macros.

[fritzmueller]

I had a short look on your changes, maybe the EURO has changed a little, see enclosed overview I got from Google AI (but I am rather sure that this is correct):   21 official EURO members in 2026, according to google AI (should be correct):     Belgia,     Bulgaria (since January, 1st 2026!)     Deutschland (Germany)     Estland, former part of russia     Finnland,     Frankreich, france     Griechenland (greece)     Irland (Ireland)     Italien (Italy)     Kroatien (croatia, since January 1st, 2023)     Lettland (latvia),  former part of russia     Litauen (lithuania),  former part of russia     Luxemburg     Malta (island in the mediterranean sea, a country of its own)     Niederlande (netherlands)     Österreich  (Austria)     Portugal     Slowakei (slovakia) - BUT NOT CZECHIA!     Slowenien (slovenia)     Spanien (spain)     Zypern (Cyprus, country in the mediterranean sea, country of its own, splitted into Greek and Turkey, Euro is for the Greek speaking part),       Further Users (extremely small countries, no official member of Euro Zone):      official usage:    Andorra (strictly spoken only a street between Spain and France with a lot of shopping malls)    Monaco (between France and Northwest Italy, a half free state)    Vatican city (pope in Italy)      inofficial usage:    Kosovo      (former YUG)    Montenegro  (former YUG) I remember that some small countries in former YUG simply use it, was reported in tv      The following EU members still have there own currencies: (according to Google AI)                  Bulgarien: Lew (BGN) - NO LONGER - see above!!!!!     Denmark: Dänische Krone (DKK)     Poland: Polnischer Zloty (PLN)     Romania: Rumänischer Leu (RON)     Sweden: Schwedische Krone (SEK)     Tschechien: Tschechische Krone (CZK) (former part Slovakia has Euro!, cz not!)     Ungarn: Ungarischer Forint (HUF)    If you need other informations, e.g. DDMMYYYY or  " ,." (1000nds separator) or something else please simply ask me. But Google AI gives a lot of information about this too.     Fritz     Sent: Wednesday, January 28, 2026 at 12:20 AM From: "Andrew Bird" ***@***.***> To: "FDOS/country" ***@***.***> Cc: "fritzmueller" ***@***.***>, "Mention" ***@***.***> Subject: Re: [FDOS/country] CI: Add validation (PR #13) andrewbird left a comment (FDOS/country#13) @fritzmueller @PerditionC I fixed up the current tables to pass validation. I'd appreciate it if you could review the Country changes especially the last, Montenegro, as I had to make most of that up. Ooh, they're using the Euro without permission - nice! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[fritzmueller]

Hi, Google AI gave me a good summary about date sort of the different european countries. I hope it can help you:   Complete Guide to European Date Formats Category 1: The "Trailing Dot" Style (Three Dots) These countries place a dot after the day, month, and year. Hungary: YYYY. MM. DD. (e.g., 2026. 01. 28.) — Year first, spaces after dots. The Balkans (Croatia, Slovenia, Serbia, Montenegro, Bosnia, North Macedonia): DD. MM. YYYY. (e.g., 28. 1. 2026.) — Spaces after dots. Finland, Estonia, Latvia: DD.MM.YYYY. (e.g., 28.1.2026.) — Usually no spaces. Category 2: The "Standard Dot" Style (Two Dots) The most common format in Europe. Dots are used as separators, but there is no dot after the year. DACH-Region: Germany, Austria, Switzerland, Luxembourg. Eastern Europe: Ukraine, Romania, Moldova, Belarus, Russia. Northern & Central Europe: Iceland, Norway, Czechia*, Slovakia*. *Note: Czechia and Slovakia use spaces: 28. 1. 2026 Category 3: The "Slash" Style (/) Common in the West, the South, and English-speaking islands. UK & Ireland: DD/MM/YYYY West & South: France, Italy, Spain, Portugal, Belgium, Greece, Malta. Category 4: The "Hyphen" Style (-) Netherlands & Denmark: DD-MM-YYYY ISO-Standard (Sweden & Lithuania): YYYY-MM-DD Category 5: Special Notations Bulgaria: DD.MM.YYYY г. (e.g., 28.01.2026 г.) — The "г." stands for "year". Poland: DD.MM.YYYY or with Roman numerals: 28.I.2026. Final Summary for your documentation: Dots (.): Used by the vast majority of Central and Eastern Europe (including Ukraine, Romania, Belarus, Moldova). Trailing Dot: Only in Hungary, the Balkan states, Finland, and the Baltic states. Slashes (/): Used in the UK and Romanic/Mediterranean countries. Hyphens (-): Used in the Netherlands and for the official Swedish/Lithuanian ISO format.   Fritz Message ID: ***@***.***

[andrewbird]

Thanks for the info, you obviously know this stuff well. I've updated the currency values in line with what Wikipedia says is the currency in use. Only Serbia differed from your AI list above, says they are still using Serbian Dinar. That's probably as much as I want to do on this at the moment.

[fritzmueller]

thanks for fixing all this. even if something should be still wrong, it is better than it was in the last 25 years. and it can be coordinated with nls now. I dont know if you know why all this? I started to fill up all files that support nls with ai languages and according to jerome i splitted it into human made files and ai made files. each of the language will have a utf-8 file for documentation and one in the correct codepage. so alltogether i will have to give ai in about 60 programs x 25 languagesx 2, cpxxx and utf-8, minus human made translations, means a lot of work. ai can create the text in utf-8 and say which country and cp I should use, but i have to create single Utf-8 files and change the languages manually to the correct cp. so the most important thing is to know language ending and codepage ending. and there were a lot of changes and problems since last august, when brazil came into discussion. And we still have some candidates where discussion is not over. mazovian, a polish subculture where i know nothing about, i will leave away latin, japanese and chinese, basque etc. maybe you have seen my german and english htmlhelp 1.1.1 files, where only less was made by ai, i needed in about three years for them, you will understand that i know that this job is not done in five minutes, but hopefully faster than htmlhelp. jim and jerome and some others know about this plan and agreed. fritz

…

Sent: Wednesday, January 28, 2026 at 3:00 PM From: "Andrew Bird" ***@***.***> To: FDOS/country ***@***.***> Cc: fritzmueller ***@***.***>, Mention ***@***.***> Subject: Re: [FDOS/country] CI: Add validation (PR #13) andrewbird left a comment (FDOS/country#13) Thanks for the info, you obviously know this stuff well. I've updated the currency values in line with what Wikipedia says is the currency in use. Only Serbia differed from your AI list above, says they are still using Serbian Dinar. That's probably as much as I want to do on this at the moment. -- Reply to this email directly or view it on GitHub: #13 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[andrewbird]

Yes I briefly had a conversation with Jerome where he explained the Human / AI split, mainly because I expressed surprise that some AI translations were replacing existing human ones (that were presumably produced by a native speaker). I'm glad they have a plan in place to manage this and as you say it's quite an undertaking.

[andrewbird]

@PerditionC don't worry about breaking / fixing the validation with your refactoring with macros clean up. I'll fix it up afterwards to work with your new scheme.

[fritzmueller]

Serbia is not part of the EU, so no Euro. They try to come in (like Turkey) but till today it didnt happen. You have to fullfill certain rules (adapt laws to EU standard etc.) first. I am not sure if you know that "EU is not Europe". Europe includes much more countries (till the Ural mountains in Russia) whereas the EU is a join of states closer to the American system with 50  states. They all have their own administration and try to work together under basic rules. A lot of european states are NOT in the EU. Hope I could explain it.   I have historical reasons why I try not to use my real name or email address in public - but now that I'm retired it is no longer so strict. A lot of people know it , so dont worry.   Fritz     Sent: Wednesday, January 28, 2026 at 3:00 PM From: "Andrew Bird" ***@***.***> To: "FDOS/country" ***@***.***> Cc: "fritzmueller" ***@***.***>, "Mention" ***@***.***> Subject: Re: [FDOS/country] CI: Add validation (PR #13) andrewbird left a comment (FDOS/country#13) Thanks for the info, you obviously know this stuff well. I've updated the currency values in line with what Wikipedia says is the currency in use. Only Serbia differed from your AI list above, says they are still using Serbian Dinar. That's probably as much as I want to do on this at the moment. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[andrewbird]

I am not sure if you know that "EU is not Europe".

Yes I'm in UK, no longer EU, but still Europe. 😄

[andrewbird]

Will have to review whether the 785 Arabic should be retained, so don't merge yet.

[andrewbird]

Renamed the me to xx to retain Middle East and added new entries for Montenegro.

[fritzmueller]

Hi, I am just a little confused:   What about Iceland, Estonia (CP775, Latvia (CP775) and Lithuania (CP775) which are separate states? Do you need more info? They use the Euro .   AI said to me that Finland and Sveden are part of the Nordic States and should also support CP865? So CP865 should be used by: Denmark, Sveden, Norway, Finland  (maybe at least added at country.sys?)   Ukrainia is one more thing: Is it correct that I have to change cp from 855 to  848 or 1125 as it is in country.sys?   Thanks for a short response. I need this infos for coordination with NLS files.   Fritz     Sent: Sunday, February 01, 2026 at 1:27 AM From: "Kenneth J Davis" ***@***.***> To: "FDOS/country" ***@***.***> Cc: "fritzmueller" ***@***.***>, "Mention" ***@***.***> Subject: Re: [FDOS/country] CI: Add validation (PR #13)   Merged #13 into master. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[andrewbird]

Hi Fritz,
we split the task. @PerditionC has a different PR #10 that deals with some of those. At the moment it has conflicts as my Czechoslovakia / Yugoslavia changes got merged first, so I did a rebase and deconflict of it as a test PR #14.

[PerditionC]

updated Ukraine with additional codepages, but 855/848 and similarly 866/1125 should be largely compatible.

I believe the Iceland, ... Sweden ... stuff is supported already.

Please see #15 for latest updates. I will try and post a build of country.sys for testing soon.