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

Fix hidden strings in Crowdin #1968

Closed
Kebap opened this issue Sep 10, 2018 · 5 comments · Fixed by #1972
Closed

Fix hidden strings in Crowdin #1968

Kebap opened this issue Sep 10, 2018 · 5 comments · Fixed by #1972
Labels
bug i18n & l10n internationalization and localization

Comments

@Kebap
Copy link
Contributor

Kebap commented Sep 10, 2018

Brief summary of issue / Description of requested feature:

Crowdin hides unexpected strings from display. Translators wrongly assume there is nothing to translate.

Steps to reproduce the issue / Reasons for adding feature:

  1. Set Crowdin Editor Settings to hide HTML Tags Displaying
  2. Look at a non-HTML string encapsulated in < and > brackets
  3. Crowdin will wrongly identify this as HTML and hide display

Error output / Expected result of feature

  1. Crowdin should be able to handle and display this legitimate text normally

Example

Following strings are obvious examples (there may be more complex):

String displayed wrongly:
grafik

Resetting the setting:
grafik

String display as expected:
grafik

@Kebap Kebap added i18n & l10n internationalization and localization bug labels Sep 10, 2018
@Kebap
Copy link
Contributor Author

Kebap commented Sep 10, 2018

Any ideas how to remedy? @Andrulko

@SlySven
Copy link
Member

SlySven commented Sep 10, 2018

TBH We should probably avoid putting texts in < and > marks...

@vadi2
Copy link
Member

vadi2 commented Sep 10, 2018

I'm down for that idea.

@Kebap
Copy link
Contributor Author

Kebap commented Sep 10, 2018

OK if that is an option then we can work around this quirk 👍

@Andrulko
Copy link

Andrulko commented Dec 3, 2018

We'll investigate this one too! Apologies, I'm not sure how this point was missed earlier :( Please ping our support team for any urgent things, I'm totally with you here and agree that current behavior is not very expected & useful. Removing &lt; and &gt; is a workaround, but not permanent I hope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug i18n & l10n internationalization and localization
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants