Skip to content

Merge master-localization into master #16261

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

escbuild
Copy link
Collaborator

@escbuild escbuild commented Jun 3, 2025

Hi , could you please review and merge this PR?

================== Word Count Statistics begin ==================
GMT Tue Jun 3 18:43:10 2025: Localization Engineer Lead for this PR is [email protected],[email protected].

Vendor Engineer for this PR is [email protected].

Localization branch is updated.
New/Updated strings status
CHS: 3 strings (24 words) are in English
CHT: 3 strings (24 words) are in English
CSY: 3 strings (24 words) are in English
DEU: 3 strings (24 words) are in English
ESP: 3 strings (24 words) are in English
FRA: 3 strings (24 words) are in English
ITA: 3 strings (24 words) are in English
JPN: 3 strings (24 words) are in English
KOR: 3 strings (24 words) are in English
PLK: 3 strings (24 words) are in English
PTB: 3 strings (24 words) are in English
RUS: 3 strings (24 words) are in English

Please note that If the word count above shows some words in English, it is because the localization team hasn't processed all the new/updated strings yet. These words will be translated in the next translation loop.

Please merge this PR anyway as it will align the localizable file(s) content with the English file(s) content and prevent any functionality issue caused from misaligned localized file(s) versus English file(s).

If you are about to release and you are concerned about these strings showing up in English, please contact your localization contact/project team. Thanks.
=================== Word Count Statistics end ==================

From build https://ls.jenkins.autodesk.com/job/CL/job/DynamoCore_CL/410/
Professional translation: all languages
Pseudo translation: none
@QilongTang
Copy link
Contributor

@ZbynekHanak-RWS I cant approve this easily because it seems the CI is switching out the Microsoft ResX Schema Version 1.3 to 2.0 and may I ask is it from some version change related to .NET10 migration? I am worried if developers' local env will be hit by this

@ZbynekHanak-RWS
Copy link
Collaborator

Hi @QilongTang , looks this is not related to .NET10 migration, as it is not supported by Loc tool yet. That's how our Loc tool generates target files using built-in .Net Parser. Would it be possible to update the source Microsoft ResX Schema Version 1.3 to 2.0 for this source? Seems this is the only Resources.en-US.resx in repo using that old .NET framework. Thank you.

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

Successfully merging this pull request may close these issues.

3 participants