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

feat: add multi-language support (Chinese, English and French) #6

Closed
wants to merge 1 commit into from
Closed

Conversation

kerms
Copy link
Contributor

@kerms kerms commented Oct 6, 2023

Used .resx resource file to achieve the localization function.
The default language is english, and auto-selected based on the system language (WPF built-in behavior).

@windowsair
Copy link
Owner

Amzing work! I had considered the feature of multi-language before, but I put it on hold due to time constraints and other reasons. Please give me some time to review your pr. 😀

@windowsair
Copy link
Owner

How about using i18n libraries like WPFLocalizeExtension? Would it be more flexible and convenient?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ci build fail:

CSC : error CS2001: Source file 'D:\a\elaphureLink\elaphureLink\elaphureLink.Wpf\Properties\Resources.Designer.cs' could not be found. 

Should we delete this?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it looks like these are modifications to the source files. Do you need to submit the changes to csproj along with them?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These files were empty(Resources.resx/Resources.resx.cs), I might delete them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it looks like these are modifications to the source files. Do you need to submit the changes to csproj along with them?

Oups, I didn't submit changes to .csproj, I'm beginner to C# and WPF, should I submit the .csproj file along with the commit ?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it looks like these are modifications to the source files. Do you need to submit the changes to csproj along with them?

Oups, I didn't submit changes to .csproj, I'm beginner to C# and WPF, should I submit the .csproj file along with the commit ?

Yes. You can submit the changes to related files such as .csproj on the basis of this patch.

@kerms
Copy link
Contributor Author

kerms commented Oct 6, 2023

How about using i18n libraries like WPFLocalizeExtension? Would it be more flexible and convenient?

😒I'm not expert in C#/WPF, I just used the first solution comes to me.

@windowsair
Copy link
Owner

How about using i18n libraries like WPFLocalizeExtension? Would it be more flexible and convenient?

😒I'm not expert in C#/WPF, I just used the first solution comes to me.

The core ideas of the two method are consistent. Maybe we can migrate to an i18n library. Now let's solve the compile issue first. 😉

@kerms
Copy link
Contributor Author

kerms commented Oct 6, 2023

I

How about using i18n libraries like WPFLocalizeExtension? Would it be more flexible and convenient?

😒I'm not expert in C#/WPF, I just used the first solution comes to me.

The core ideas of the two method are consistent. Maybe we can migrate to an i18n library. Now let's solve the compile issue first. 😉

I will create a new PR tomorrow by cleaning all non-staged changes on my local repo. I close this PR for the moment.

@kerms kerms closed this Oct 6, 2023
@windowsair
Copy link
Owner

I

How about using i18n libraries like WPFLocalizeExtension? Would it be more flexible and convenient?

😒I'm not expert in C#/WPF, I just used the first solution comes to me.

The core ideas of the two method are consistent. Maybe we can migrate to an i18n library. Now let's solve the compile issue first. 😉

I will create a new PR tomorrow by cleaning all non-staged changes on my local repo. I close this PR for the moment.

Thank you for your commit!
You don't need to close the this pr, you can just submit a new commit on this pr and push it to github. Your new modification will be visible on this page. 😉

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

Successfully merging this pull request may close these issues.

2 participants