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

[BUG]: Misformatted Text - Special character - Portuguese #5200

Open
adhiamboperes opened this issue Oct 18, 2023 · 8 comments
Open

[BUG]: Misformatted Text - Special character - Portuguese #5200

adhiamboperes opened this issue Oct 18, 2023 · 8 comments
Assignees
Labels
bug End user-perceivable behaviors which are not desirable. Impact: High High perceived user impact (breaks a critical feature or blocks a release). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.

Comments

@adhiamboperes
Copy link
Collaborator

Describe the bug

The special caracter "Ã" is unformatted on chapter 4 of Fractions.

Steps To Reproduce

  1. Open Fraction topic
  2. Open chapter 4
  3. Second screen already presents the bug

Expected Behavior

Text should be "não" "questão" "são"

Screenshots/Videos

image

What device/emulator are you using?

No response

Which Android version is your device/emulator running?

No response

Which version of the Oppia Android app are you using?

0.11 Beta

Additional Context

This also happens on web at: https://www.oppia.org/explore/rfX8jNkPnA-1?story_url_fragment=matthew-visits-the-bakery&topic_url_fragment=fractions&classroom_url_fragment=math&node_id=node_4

The affected asset file is rfX8jNkPnA-1.pb

@adhiamboperes adhiamboperes added bug End user-perceivable behaviors which are not desirable. Impact: High High perceived user impact (breaks a critical feature or blocks a release). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. labels Oct 18, 2023
@adhiamboperes
Copy link
Collaborator Author

I found this in assets as far back as beta 0.9

@seanlip
Copy link
Member

seanlip commented Oct 18, 2023

Update: This has now been fixed on the website.

@Tushar-kalsi
Copy link

Hi ,
Can i get the opportunity to work on this ??

@adhiamboperes
Copy link
Collaborator Author

Hi , Can i get the opportunity to work on this ??

Hi, there's nothing to be done here at the moment - the issue has been fixed on web.
Can you look at #4072 or select an item from #5169?

@adhiamboperes adhiamboperes changed the title [BUG]: Misformatted Text - Special caracter - Portuguese [BUG]: Misformatted Text - Special character - Portuguese Oct 27, 2023
@seanlip
Copy link
Member

seanlip commented Apr 29, 2024

@adhiamboperes Just to check, is this issue supposed to still be open (given that it's been fixed in the content)? Asking since it's on the hotlist for the 0.12 release.

Thanks!

@adhiamboperes
Copy link
Collaborator Author

@seanlip, we need to download the latest assets to go out in 0.13 for this to be closed. I have moved the issue to the 0.13 milestone.

@Rd4dev
Copy link
Collaborator

Rd4dev commented Jul 2, 2024

Hi @adhiamboperes, I reviewed Chapter 4 of Fractions in Portuguese and found that every special character "Ã" is formatted correctly ( "não" "questão" "são"). However, I did find three instances where the statements are not properly translated.

1. next

36

2. great

38

3. $

37

Other reference Instances where they are properly translated

39

Although this isn't directly related to the unformatted "Ã," I thought it would be helpful to include this information here for reference.

@seanlip
Copy link
Member

seanlip commented Sep 10, 2024

Hi @Rd4dev, thank you so much for finding these! I confirm that "próxima" and "Ótimo!" have been corrected on the website. Note that R$ is correct though (it is the unit of currency in Brazil, reais), so I did not fix that one.

@adhiamboperes @BenHenning FYI re the content updates here, and just noting generally that this bug on the Android app should be fixed the next time the Android content is downloaded. (Not sure if that means we can close this issue, or if we need to wait until the content download is done in order to close it.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug End user-perceivable behaviors which are not desirable. Impact: High High perceived user impact (breaks a critical feature or blocks a release). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.
Development

No branches or pull requests

5 participants