-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
Import report / Import log #1558
Labels
enhancement
Adding or requesting a new feature.
undecided
These features might not be implemented. Can be prioritized by sponsorship.
Comments
This really doesn't scale - let's take translations of Weblate as an example, those consist of 1684 strings. Do you think that showing 1684 messages will do any good? |
nijel
added
the
undecided
These features might not be implemented. Can be prioritized by sponsorship.
label
Jul 18, 2017
Le 17 juillet 2017 12:22:40 UTC+02:00, "Michal Čihař" <notifications@github.com> a écrit :
This really doesn't scale - let's take translations of Weblate as an
example, those consist of 1684 strings. Do you think that showing 1684
messages will do any good?
For every changes yes.
For unmatched strings, it's a warning, so yes also.
For ignored, indeed, it may be useless.
The relevant size of a component (number of strings) depends on the developers. 1600 strings is too much, you should probably split it. But it's no big deal.
Is there much file import on hosted.w? Are you afraid of the database size?
…--
Jean-Baptiste Holcroft
|
Actually 1600 strings is somewhat usual (at least based on numbers I see on Hosted Weblate, the average is 1100). The database size is not concern, but I would like to avoid storing things which nobody will ever use :-). |
Le 19 juillet 2017 12:02:56 UTC+03:00, "Michal Čihař" <notifications@github.com> a écrit :
Actually 1600 strings is somewhat usual (at least based on numbers I
see on Hosted Weblate, the average is 1100).
The database size is not concern, but I would like to avoid storing
things which nobody will ever use :-).
Fair point! But if import perfectly worked, it would probably be no used at all ;)
Maybe a text file would do the job, and after a while, you'll decide weather it is much used or not. Access log will help use to see usage, and bugtracker will help to see if there is still issues to track.
--
Jean-Baptiste Holcroft
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Adding or requesting a new feature.
undecided
These features might not be implemented. Can be prioritized by sponsorship.
Steps to reproduce
Actual behaviour
Weblate tells you about the number of updates, changes, errors, but gives no details.
Expected behaviour
It would be great to have an "import report", giving you every details, something like a log:
In addition, I assume we should may have a single line in history to access this log instead of multiple lines.
It had this idea when testing #1547, because the user don't know for sure if his work is fully uploaded or not and to make changes manually in case of a rush. Note: as a workaround for this, we can still make a second export & search manually.
The text was updated successfully, but these errors were encountered: