[Weter]

Hello.
Just tried to manually update testing version 1.3.1-335 to 1.3.1-370
After replacing files, menu.exe began through an error:

System.NullReferenceException: Ссылка на объект не указывает на экземпляр объекта.
   в ORTS.MainForm.SaveOptions() в C:\Jenkins\jobs\Open Rails Testing\workspace\Source\Menu\MainForm.cs:строка 701
   в ORTS.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e) в C:\Jenkins\jobs\Open Rails Testing\workspace\Source\Menu\MainForm.cs:строка 290
   в System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
   в System.Windows.Forms.Form.CheckCloseDialog(Boolean closingOnly)

no one string of menu is filled with text,
closing window is possible only bu task manager.
rewriting 1.3.1-335 files back, causes the same error with version -335, which worked without issues till last night.
1.3.1-285 version behaves the same way too.
only 1.3.1-133 runs well.

What i did wrong and how to fix the problem?
This situation makes trouble.
Spent some priceless hours and nerves for experiments, I've inserted Menu.exe from -133 build to -370 and it works, but i can't access options.
This is a cheat, but not resolve.
I installed useless directX (they wasn't needed yesterday), failed to install .Net frameworks 4.8(as newer version is already present within the system)
Rolling Windows back to 14.06 didnt solve the problem.
There was something about "Load From Remote Sources" and .Net...
Where can I find such switcher?

[YoRyan]

I would try uninstalling and reinstalling OR first. It's easy to corrupt the install if you manually replace the files like that. OR was not designed to mix and match executables and DLL's from different testing versions.

Alternatively, forget about the update mechanism altogether and just build from GitHub with Visual Studio. As a translator, I'm surprised you're not doing so already.

[Weter]

Thanks,
but pure install of 1.3.1-370 to new folder just throw that exception.
And I tend to suspect the correlation of that with system stability, as Derek said, what was shown at stability logs (I mean TSRE freezing, occured at the same time with some auto-updates of the system)

And what the heck is with "Load From Remote Sources"? As ORTS is local application.

Clearing and re-writing registry doesn't solve problem.
Menu.exe throws exception immediately, just after window appearance, but now, though, can be closed by mouse click on cross, without task manager, but only the first time.

Posted 09 July 2021 - 12:56 AM
Well, as no one else was interested...
Following the path of logical reflection...
I have checked my hypothesis today...
Remembering, what have I done, before everything failed to work and analysing, what Menu.exe do and how it works, what it involves...
I have re-writed updated localization-*.dll's and everything began work again.
So I suspect that was spaces around strings, which Chris modified to show tips icons at options page.

[Weter]

Version T1.3.1-1890 fails to work with russian locales, provided with it.
I have made a patch with proper *.dll-s (available, where always) and have sent new *.po-files to GitHub
If they will be declined again, i believe, new versions will not work with russian language as well.

[Weter]

New issue:
This is related with this topic too:
http://www.elvastowe...work-cas-policy
I have downloaded new testing version T1.3.1-2065 and that issue, mentioned above returned.
Using rusification patch from previous version didn't help: No menu entries.
So, I couldn't access options screen for changing language to English.
Then, I removed ru subfolder to force that change.
Program started working normally (in English)
Then I revised translations and with refreshed dll's it worked well too.

But, then I've noticed a strange thing: there was another language option in addition to System, English and Russian; the "Pseudo" entry with some ?-signs, wrote in Greek letters. Changing language to it returns issue.

So, what is pseudo, and update-pseudo.bat?

[ebnertra000]

The pseudo-language was meant to be English, using weird letters that looked like English letters, I think as a joke. I've used it a few times because I thought it was amusing

[Weter]

Seems to me like greek alphabet...

The problem, as I see it now: some code changes "shift" something among strings, so previous locale *.dll's begin to cause errors. During review/approve time, new versions released.

[James Ross]

Weter, on 28 September 2021 - 09:58 AM, said:

But, then I've noticed a strange thing: there was another language option in addition to System, English and Russian; the "Pseudo" entry with some ?-signs, wrote in Greek letters. Changing language to it returns issue.

So, what is pseudo, and update-pseudo.bat?

It is pseudolocalization: you have a special "language" where everything is automatically "translated" into something that is mostly still readable but also obviously not the original English. This allows the programmers to make sure everything can be translated.

This is what it looked like in Windows 7:

https://i.stack.imgur.com/bFd6p.png

[James Ross]

Weter, on 28 September 2021 - 12:00 PM, said:

Simulation of translation with verifying capability? Right.
It messed me, because "pseudo" is Greek word itself :)
Thanks for hint.
I've seen it the first time yesterday at ORTS. Forgot to remove from testing?

While it's primarily for developers, we didn't feel like it was worth the extra effort to hide/remove it from other users. It's been there for years. :)

Weter, on 28 September 2021 - 12:00 PM, said:

But what can be wrong with locales compatibility?

I'm afraid I have no idea about the other issues in this thread.

[Weter]

So, there is no need for me-to use update-pseudo.bat, as I understand?
I use now only update-templates and update-DLLs (rarely-update.bat)
Well, I will keep on investigating circumstances of that, as possible, and report.
It's pity, that localization, uploaded through GitHub becomes unworkable so soon, and uploading patches here is needed.