Office 2024 LTSC really is IMHO "Beta status" -- I'd stick with Office 2021 LTSC or whatever you already have until Office 2024 is really "work place ready".
5 x LG 25MS500-B - 1 x 24MK430H-B - 1 x Wacom Pro 22" Touch Screen Tablet
Screen Resolution
All over the place
Hard Drives
Too many to list.
OS on Samsung 1TB 870 QVO SATA
PSU
Silverstone 1500
Case
NZXT Phantom 820 Full-Tower Case
Cooling
Noctua NH-D15 Elite Class Dual Tower CPU Cooler / 6 x EziDIY 120mm / 2 x Corsair 140mm somethings / 1 x 140mm Thermaltake something / 2 x 200mm Corsair.
Still no Lang ISL which I've had since Office 2010.
OK not a "huge majority language" but if W11 supports it and previous versions of office have it why is it no longer in LTSC 2024. I understand in a "new Dev release" but surely an LTSC release should incorporate previous languages that were supported. Nothing against English etc but why should one HAVE to use it on apps that previously supported other languages.
It's not that difficult to do this for a GUI -- for all the screen elements create a data dictionary and then simply for the relevant elements just translate -- so you have a basic set of screen dialogs, a data dictionary with the screen elements (essentially as TEXT labels) in it and then just run the elements through the translator. When composing the screen you just get the appropriate elements from the Data dictionary. This works for any number of languages -- all you need is ONE standard screen, a list of the data elements and a link to the DDIC to pic up the appropriate translation before sending to screen. Then the screen is stored in a "Screen catalog" so translation doesn't need to be done on every screen refresh / send list.
Don't Windows programmers know ANYTHING about "Dynamic elements" etc etc.
