Hello translators,
When reading the GNOME 3.32 release notes, I noticed this page: https://help.gnome.org/misc/release-notes/3.32/i18n.html.en
It tells us the list of languages with more than 80%.
I feel like it could be interesting to start producing something equivalent for Fedora.
Thanks to Sundeep Anand, we now have Transtats, and the following page looks like to contain the required information: https://transtats.fedoraproject.org/releases/view/fedora-30 (remember to click "Detailed" on top right.
If we want to do such things, I assume it means: * agree on the minimum list of packages to take into account * validate the values of transtats is good for these package (we need to validate one or two language results per package) * draft the appropriate documentation page
What do you think of this? Are you willing to help so we have it for F30? (according to the schedule, it means we have one month to produce it)
In the future, I hope this work may be automated and provided directly by Transtats ;)
On Mon, Mar 18, 2019 at 1:44 PM Jean-Baptiste Holcroft jean-baptiste@holcroft.fr wrote:
Hello translators,
When reading the GNOME 3.32 release notes, I noticed this page: https://help.gnome.org/misc/release-notes/3.32/i18n.html.en
It tells us the list of languages with more than 80%.
I feel like it could be interesting to start producing something equivalent for Fedora.
Thanks to Sundeep Anand, we now have Transtats, and the following page looks like to contain the required information: https://transtats.fedoraproject.org/releases/view/fedora-30 (remember to click "Detailed" on top right.
If we want to do such things, I assume it means:
- agree on the minimum list of packages to take into account
I suggest we use base list of packages required by the Edition/Spin being reported for. That way we don't have to define this list.
- validate the values of transtats is good for these package (we need
to validate one or two language results per package)
- draft the appropriate documentation page
I wonder if the transstats folks could code up a quick report for us that would get us to automation faster.
regards,
bex
What do you think of this? Are you willing to help so we have it for F30? (according to the schedule, it means we have one month to produce it)
In the future, I hope this work may be automated and provided directly by Transtats ;) _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
On Mon, Mar 18, 2019 at 10:30 PM Brian (bex) Exelbierd bexelbie@redhat.com wrote:
On Mon, Mar 18, 2019 at 1:44 PM Jean-Baptiste Holcroft jean-baptiste@holcroft.fr wrote:
Hello translators,
When reading the GNOME 3.32 release notes, I noticed this page: https://help.gnome.org/misc/release-notes/3.32/i18n.html.en
It tells us the list of languages with more than 80%.
I feel like it could be interesting to start producing something equivalent for Fedora.
Thanks to Sundeep Anand, we now have Transtats, and the following page looks like to contain the required information: https://transtats.fedoraproject.org/releases/view/fedora-30 (remember to click "Detailed" on top right.
Thanks :)
If we want to do such things, I assume it means:
- agree on the minimum list of packages to take into account
I suggest we use base list of packages required by the Edition/Spin being reported for. That way we don't have to define this list.
- validate the values of transtats is good for these package (we need
to validate one or two language results per package)
- draft the appropriate documentation page
I wonder if the transstats folks could code up a quick report for us that would get us to automation faster.
I guess, this should be quick. Let me see, to develop and ship in next release 0.7.2 Three important measures: (1) Package List (#41 https://github.com/transtats/transtats/issues/41), (2) Language Set and (3) Translation Threshold Feel free to add / append issues at https://github.com/transtats/transtats/issues
regards,
bex
What do you think of this? Are you willing to help so we have it for F30? (according to the schedule, it means we have one month to produce it)
In the future, I hope this work may be automated and provided directly by Transtats ;)
sure!
regards, sundeep
trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
-- Brian (bex) Exelbierd | bexelbie@redhat.com | bex@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
Le 2019-03-19 06:19, Sundeep Anand a écrit :
On Mon, Mar 18, 2019 at 10:30 PM Brian (bex) Exelbierd bexelbie@redhat.com wrote:
I suggest we use base list of packages required by the Edition/Spin being reported for. That way we don't have to define this list.
- validate the values of transtats is good for these package (we
need
to validate one or two language results per package)
- draft the appropriate documentation page
I wonder if the transstats folks could code up a quick report for us that would get us to automation faster.
Interesting, what is this list and how do we access it? Without knowing it, I'm afraid to see a huge list of technical packages quite far from the minimum set of packages for a correct user-experience.
I guess, this should be quick. Let me see, to develop and ship in next release 0.7.2
Well, that's good to have your help for automation, what is the contribution you expect from me/translators?
On Tue, Mar 19, 2019 at 6:39 PM Jean-Baptiste Holcroft < jean-baptiste@holcroft.fr> wrote:
Le 2019-03-19 06:19, Sundeep Anand a écrit :
On Mon, Mar 18, 2019 at 10:30 PM Brian (bex) Exelbierd bexelbie@redhat.com wrote:
I suggest we use base list of packages required by the Edition/Spin being reported for. That way we don't have to define this list.
- validate the values of transtats is good for these package (we
need
to validate one or two language results per package)
- draft the appropriate documentation page
I wonder if the transstats folks could code up a quick report for us that would get us to automation faster.
Interesting, what is this list and how do we access it? Without knowing it, I'm afraid to see a huge list of technical packages quite far from the minimum set of packages for a correct user-experience.
I guess, this should be quick. Let me see, to develop and ship in next release 0.7.2
Well, that's good to have your help for automation, what is the contribution you expect from me/translators?
Basic implementation is here: https://transtats.fedoraproject.org/releases/view/fedora-30 (select 'Threshold Based' view) Currently it's including all packages (those having proper branch mapping[1]). However, we have an issue for "Package Sets" ( https://github.com/transtats/transtats/issues/41) Package sets seem meaningful as they can improve 'Threshold Based' view, shall help in creating graph rules and running multiple jobs at once.
[1] https://transtats.fedoraproject.org/quick-start
trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
Le 18/03/2019 à 17:58, Brian (bex) Exelbierd a écrit :
On Mon, Mar 18, 2019 at 1:44 PM Jean-Baptiste Holcroft jean-baptiste@holcroft.fr wrote:
Hello translators,
When reading the GNOME 3.32 release notes, I noticed this page: https://help.gnome.org/misc/release-notes/3.32/i18n.html.en
It tells us the list of languages with more than 80%.
I feel like it could be interesting to start producing something equivalent for Fedora.
I suggest we use base list of packages required by the Edition/Spin being reported for. That way we don't have to define this list.
Dear community,
I now have a working proof of concept!
Here is the code: https://pagure.io/fedora-localization-statistics
You can see the f30 stats per package in the results/f30/ folder.
Still is some bugs to fix and A LOT of validations to do...
These files are language files I don't handle yet (or need to confirm aren't a bug):
todo_aresource.txt todo_auto.txt todo_joomla.txt todo_po-mono.txt todo_properties.txt todo_strings.txt todo_webextension.txt
A few packages crash because of weird infinite symlinks: see errors.txt
The libreoffice package is too big. It crashes translation_finder.
Anyone with time to help on this? It requires really basic bash/python scripting skills.
Le 26/04/2019 à 06:33, Jean-Baptiste Holcroft a écrit :
Dear community,
I now have a working proof of concept!
Hello,
please find in this repo the results of the fedora 30 Workstation Live CD:
https://pagure.io/fedora-localization-statistics/blob/master/f/results/f30/_...
In the coming days, I'll try to produce and article from these numbers.
You are welcome to help either by spotting bug or thinking at the analysis we could do from these numbers.
This does not include the translation from Libreoffice and Firefox.
Why?
* Libreoffice because it's too big and crashes the translation detector.
* Firefox, because it's too complicated, too many files, too many exceptions.
I'll improve this someday, it's bad not to include it.
In the same time, these project have a sufficient amount of contributors/visibility to grow.
Have a nice day!