Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Russian language #243

Open
Anixx opened this issue Nov 7, 2019 · 9 comments
Open

No Russian language #243

Anixx opened this issue Nov 7, 2019 · 9 comments

Comments

@Anixx
Copy link

Anixx commented Nov 7, 2019

Even though the original Winfile had it

@craigwi
Copy link
Contributor

craigwi commented Nov 7, 2019

See discussion in #77. Also, all of the original language files that I could recover are in src\origrc.

@clzls
Copy link
Contributor

clzls commented Nov 11, 2019

If you can read Russian, you may check is this translation ok:
https://github.com/microsoft/winfile/blob/master/src/origrc/winfile.ru-RU.rc
https://github.com/microsoft/winfile/blob/master/src/origrc/winfile.en-US.rc

and we may add Russian into the release in the future, if you want to help... (Since we are not native Russian speakers...)

@Anixx
Copy link
Author

Anixx commented Nov 11, 2019

How can I check it if it is displayed with garbage symbols?

@ZanderBrown
Copy link

GitHub/Browser has probably assumed UTF which code_page(1251) isn't, try changing browser encoding/opening locally

@clzls
Copy link
Contributor

clzls commented Nov 17, 2019

See discussion in #77. Also, all of the original language files that I could recover are in src\origrc.

Like Polish, the original rc files of other languages also need to be converted to UTF-8...
(But it seems that only ru-RU is totally unreadable? Even zh-CN, ja-JP, ko-KR are fine...)

@clzls
Copy link
Contributor

clzls commented Jun 20, 2024

How can I check it if it is displayed with garbage symbols?

@Anixx Repaired with PR #250 and merged, now it is readable. But I don't know how to "convert"/"adapt" a single .rc file into res_ru-RU.rc suggest_ru-RU.db winfile_ru-RU.dlg automatically. May @craigwi have any good idea?

@craigwi
Copy link
Contributor

craigwi commented Jun 20, 2024

In the current sources res_en-US.rc includes winfile_en-US.dlg. I don't know why this was separated. res_ru-RU.rc appears to include content for both and so it might be possible to just add that one file and update the #include and other stuff. suggest_ru-RU.db would have to be created from scratch (e.g., by copying another language).

@clzls
Copy link
Contributor

clzls commented Jun 24, 2024

In the current sources res_en-US.rc includes winfile_en-US.dlg. I don't know why this was separated. res_ru-RU.rc appears to include content for both and so it might be possible to just add that one file and update the #include and other stuff. suggest_ru-RU.db would have to be created from scratch (e.g., by copying another language).

I see. I may be able to carry out some tests then. For the latter step we still need some native speakers of Russian to do that though...

@malxau-msft
Copy link
Contributor

In the current sources res_en-US.rc includes winfile_en-US.dlg. I don't know why this was separated.

I looked into this; it was split from the initial 1991 fork. I'm 90% sure this is an artifact of the limitations of the 3.0 Dialog Editor; we didn't have integrated resource editing back then, so the dialog editor only understood dialog resources. It reads the (compiled) .res file and writes the (textual) .dlg file containing only dialogs. If they were in one .rc file, the dialog editor could not have been used.

Since res_rc-RU.rc is extracted from a binary, it didn't preserve its original source structure.

suggest_ru-RU.db would have to be created from scratch (e.g., by copying another language).

For the latter step we still need some native speakers of Russian to do that though...

All the strings are in the .rc, right? 1101-1118 and 1150-1155 are all there, it's just turning these back into macros.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants