Bug 1672385 - How does the module description translation reach end-users?
Summary: How does the module description translation reach end-users?
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1690143 (view as bug list)
Depends On:
Blocks: 1690143
TreeView+ depends on / blocked
 
Reported: 2019-02-04 19:59 UTC by jibecfed
Modified: 2022-06-08 00:47 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 00:47:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description jibecfed 2019-02-04 19:59:50 UTC
Hi,

once translated on Zanata, what's the process for the translation to reach the end-user?

I finished translation last week, but I can't see any localized content with "sudo dnf module list" on Fedora 29.

https://fedora.zanata.org/iteration/view/fedora-modularity-translations/f29/languages/fr

Thanks for your help!

Comment 1 Parag Nemade 2019-03-19 11:12:39 UTC
(In reply to jibecfed from comment #0)
> Hi,
> 
> once translated on Zanata, what's the process for the translation to reach
> the end-user?
> 
> I finished translation last week, but I can't see any localized content with
> "sudo dnf module list" on Fedora 29.
> 
> https://fedora.zanata.org/iteration/view/fedora-modularity-translations/f29/
> languages/fr

Maybe Stephen knows more about it as he is the maintainer of that Zanata project.

Comment 2 Stephen Gallagher 2019-03-19 12:10:46 UTC
At the moment, the translations are not reaching the repodata because of limitations on my time. I had a mostly-written patch to Pungi to pull these in but it got put aside due to more urgent issues. I'm going to try to get back to it soon.

Essentially, we ended up having to rewrite libmodulemd to a new API (https://sgallagh.fedorapeople.org/docs/libmodulemd/latest/) and this meant that the work I had done on the translations was no longer going to work.

Sorry for the delay on this.

Comment 3 jibecfed 2019-04-02 12:30:14 UTC
Thanks for your answer!

It gives a good overview of the past, but it lacks a few information about the future ;)
What's the amount of work left?
Is there some code somewhere?
Can someone help you?

At the moment, the module content represents 2000 words and we have 15.000 words translated.
It means translators liked the idea and are willing to help :) But also that they are working for nothing :p
Any chance to have up-to-date content to translate even if publication comes later?

Comment 4 Stephen Gallagher 2019-04-25 15:13:58 UTC
Sorry for the delay. I've been working out the details on this and this has now been scheduled.

I'll be mentoring an Outreachy candidate to work on this during their internship (which runs May to August).

The internship will have several phases, the first of which will be to extract the translatable strings from the most up-to-date content and submit it to Zanata. So I'd give a rough estimate of end-of-May for having this back in place for translators to start on.

And yes, there's some existing code at https://github.com/fedora-modularity/ModulemdTranslationHelpers that we can work from.

Comment 5 jibecfed 2019-05-28 21:22:10 UTC
Hi Stephen, is your candidate on schedule? ;)

Comment 6 jibecfed 2019-05-28 21:26:23 UTC
*** Bug 1690143 has been marked as a duplicate of this bug. ***

Comment 7 Stephen Gallagher 2019-05-28 23:25:35 UTC
Yes, work is under way, but as I said, it’s going to be the student’s project for the summer. It’s still in initial stages right now.

Comment 8 Ben Cotton 2019-08-13 17:09:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 9 Ben Cotton 2019-08-13 18:55:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 10 Ben Cotton 2020-11-03 15:08:59 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Ben Cotton 2021-02-09 15:09:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 12 Ben Cotton 2022-05-12 16:29:20 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 13 Ben Cotton 2022-06-08 00:47:28 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.