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

The [キロ] character is not displayed correctly in VictoryLabel. #2912

Closed
2 tasks done
Developer1103 opened this issue Oct 9, 2024 · 5 comments
Closed
2 tasks done
Labels
Type: Bug 🐛 Oh no! A bug or unintentional behavior

Comments

@Developer1103
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct

Victory version

36.4.0

Code Sandbox link

No response

Bug report

Hi.
In VictoryLabel on iOS, it is displayed as [キロ]->[], [メートル]->[].
If you could teach me how to display it as [キロ], [メートル], I would be grateful. 
Please help me.

Steps to reproduce

No response

Expected behavior

No response

Actual behavior

No response

Environment

- Device:iPhone
- OS:iOS
- Node:
- npm:
@Developer1103 Developer1103 added the Type: Bug 🐛 Oh no! A bug or unintentional behavior label Oct 9, 2024
@coston
Copy link
Contributor

coston commented Nov 18, 2024

Hey @Developer1103, thanks for creating this issue. I've confirmed that this issue exists. It looks like something is forcing ligatures to be rendered in iOS, but only when using the label component.

image

@coston
Copy link
Contributor

coston commented Nov 18, 2024

The source of the issue is react-native-svg, which Victory uses to render the VictoryLabel text.

The quick fix is to simply set fontVariantLigatures: "none" in your styles.

<VictoryLabel
          text="メートル Coston"
          x={150}
          y={200}
          textAnchor="middle"
          style={{
            fontSize: 20,
            fill: "black",
            fontVariantLigatures: "none",
          }}  
        />

@coston
Copy link
Contributor

coston commented Nov 18, 2024

Note: the issue does not exist on Android
image

@Developer1103
Copy link
Author

Thank you so much for your help.
I will check it out.
Please continue to take care of me.

@Developer1103
Copy link
Author

I was able to solve it.
Thank you very much for your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug 🐛 Oh no! A bug or unintentional behavior
Projects
None yet
Development

No branches or pull requests

2 participants