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

Confusing naming of converted downloads #5515

Closed
tomkolp opened this issue Feb 25, 2021 · 10 comments · Fixed by #5578
Closed

Confusing naming of converted downloads #5515

tomkolp opened this issue Feb 25, 2021 · 10 comments · Fixed by #5578
Assignees
Labels
bug Something is broken. naming Discussions about naming Weblate features.
Milestone

Comments

@tomkolp
Copy link
Contributor

tomkolp commented Feb 25, 2021

image
image
This can cause a problem when importing.

@tomkolp
Copy link
Contributor Author

tomkolp commented Feb 25, 2021

Problem with source

@tomkolp tomkolp closed this as completed Feb 25, 2021
@github-actions
Copy link

The issue you have reported is resolved now. If you don’t feel it’s right, please follow it’s labels to get a clue and take further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

@tomkolp
Copy link
Contributor Author

tomkolp commented Feb 25, 2021

image
I have created a new component marked as a glossary. I used the file from the screen. The explanation is displayed as a comment.

@tomkolp tomkolp reopened this Feb 25, 2021
@nijel
Copy link
Member

nijel commented Feb 25, 2021

There are two ways of getting files from Weblate:

  • The original file as is stored in the repository. This follows as closely as possible original format and does not include any additional metadata. This is the first option in the download menu.
  • Converted files for offline usage. These attempt to fit as much information as possible into the file for offline usage. Often this leads to putting content into developer comments as most formats do not support anything like suggestions or different source of comments. These are all the other options in the download menu.

obrazek

When you download the files using the second method and use it in Weblate the different behavior is expected.

What we really need is to set correctly expectations on the converted downloads.

@orangesunny Please can you take a look at this? This is a similar issue to what YouGov has hit...

@tomkolp
Copy link
Contributor Author

tomkolp commented Feb 25, 2021

If comments and explanations are exported, the import should take them into account.

@nijel
Copy link
Member

nijel commented Feb 25, 2021

Nearly all things from Weblate are included in the comments and there was no intention to make it machine readable, so in the current form the import is not possible. (I think there is some issue on this)

@tomkolp
Copy link
Contributor Author

tomkolp commented Feb 26, 2021

After moving from Smartcat to weblate, I have 5 glossaries. They all have 150,000 strings and over 20,000 comments. I would like to import comments as "explanations". Showing explanations in the glossary is really great. Unfortunately at the moment I have to do it manually, so translators use google sheet to find "explanations"
I think this is a big problem for users migrating to Weblate from other translation platforms.
Edit:
I checked that none of the formats available in weblate does not support the explanations. After restoring a backup "Borg" explanation will be restored?

@nijel
Copy link
Member

nijel commented Mar 2, 2021

The explanation is stored in the Weblate database only, I've just explained this in #5517 (comment)

@nijel nijel changed the title Problem with exporting to tbx (comment = explanation) Confusing naming of converted downloads Mar 2, 2021
@nijel
Copy link
Member

nijel commented Mar 2, 2021

Let's deal with clarification of the download naming here and cover the glossary explanations in #5519.

@nijel nijel added bug Something is broken. naming Discussions about naming Weblate features. labels Mar 2, 2021
@nijel nijel added this to the 4.5.1 milestone Mar 2, 2021
nijel added a commit to nijel/weblate that referenced this issue Mar 4, 2021
We do not want to introduce confusion here by offering options.

See WeblateOrg#5515
nijel added a commit to nijel/weblate that referenced this issue Mar 4, 2021
- Detailed options are gone from the menu, only original file is there
- There customize download lists formats in line to be more compact
- The customize page now includes quick links to download most common
  options by one click

Fixes WeblateOrg#5515
nijel added a commit that referenced this issue Mar 4, 2021
- Detailed options are gone from the menu, only original file is there
- There customize download lists formats in line to be more compact
- The customize page now includes quick links to download most common
  options by one click

Fixes #5515

Co-authored-by: Benjamin Alan Jamie <benjamin@weblate.org>
Co-authored-by: Allan Nordhøy <epost@anotheragency.no>
Co-authored-by: Golubev Alexander <fatzer2@gmail.com>
@github-actions
Copy link

github-actions bot commented Mar 4, 2021

Thank you for your report, the issue you have reported has just been fixed.

  • In case you see a problem with the fix, please comment on this issue.
  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken. naming Discussions about naming Weblate features.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants