Skip to content

Conversation

@notlin4
Copy link

@notlin4 notlin4 commented Sep 30, 2024

No description provided.

@stale
Copy link

stale bot commented Nov 30, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 30, 2024
@Intelli Intelli removed the stale label Nov 30, 2024
@stale
Copy link

stale bot commented Apr 12, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 12, 2025
@Intelli Intelli removed the stale label Apr 12, 2025
@stale
Copy link

stale bot commented Jun 11, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 11, 2025
@Intelli Intelli removed the stale label Jun 12, 2025
@stale
Copy link

stale bot commented Aug 11, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 11, 2025
@Intelli Intelli removed the stale label Aug 11, 2025
@Intelli
Copy link
Contributor

Intelli commented Sep 9, 2025

":" shouldn't be replaced with ":" due to server-side parsing of the character.

@notlin4
Copy link
Author

notlin4 commented Sep 11, 2025

":" shouldn't be replaced with ":" due to server-side parsing of the character.

I'm a bit confused by that. My understanding is that if is used within a string value, it should not interfere with server-side parsing. Most parsers treat such Unicode characters as regular data.

@Halogly
Copy link
Contributor

Halogly commented Nov 2, 2025

":" shouldn't be replaced with ":" due to server-side parsing of the character.

I'm a bit confused by that. My understanding is that if is used within a string value, it should not interfere with server-side parsing. Most parsers treat such Unicode characters as regular data.

A few months ago, new translatable terms were added, which you can update. You can refer to the Simplified Chinese configuration, which is currently complete in Simplified Chinese. #796

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