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

[Crowdin] <a> tag URL link identification issue #408

Open
littlegolden opened this issue Jan 20, 2022 · 2 comments
Open

[Crowdin] <a> tag URL link identification issue #408

littlegolden opened this issue Jan 20, 2022 · 2 comments

Comments

@littlegolden
Copy link
Contributor

littlegolden commented Jan 20, 2022

Some strings are incorrectly split into two parts for unknown reasons, and this happens in every language.

For example, consider two strings (actually one string but divide into separate string):
https://crowdin.com/translate/flarum-docs/16/en-de#11984 (the tag opens here but does not close)
https://crowdin.com/translate/flarum-docs/16/en-de#11986 (and this is a continuation of the string and here the tag closes)

So I emailed Crowdin Support, what they said seems like this needs to be handled by admins of docs project on Crowdin.

I think that the source file just needs to be updated so that the strings are displayed correctly.

image

how to solve?

  1. re-create doc project on Crowdin?
  2. or delete translations and re-translate?

None of these sounds easy to implement.

@littlegolden littlegolden changed the title <a> tag identification issue on Crowdin [Crowdin] <a> tag URL link identification issue Jan 20, 2022
@askvortsov1
Copy link
Member

I think that the source file just needs to be updated so that the strings are displayed correctly.

Have they mentioned anything about how exactly the source files should be changed so that links are processed correctly?

@littlegolden
Copy link
Contributor Author

got replies from Crowdin Support Team:

Crowdin:

Hi there,

Hope you're staying safe and sound these days 😃

Just wanted to say that we've tested everything on our side and file bugs.md is uploaded well, so we suppose that you had older md exporter version. In this case we recommend updating a file

Could you please update bugs.md and let us know about the results?

Thank you

Customer Success Manager
2022.1.31

me:

Hi Nataliia Milian,

Did you mean that project manager needs to upload a new file of the original English file? or translater need to upload a new translated file which going to be translated?

Crowdin:

Hello,

The manager should to remove old version of the source file and upload new one

Please let me know if any other question arise.

Customer Success Manager
2022.2.11

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

No branches or pull requests

2 participants