This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1305340 - DNF message "Upgrading" at Zanata translation defect. is this Present Progressive ? or , is Gerund? Grammar problem.
DNF message "Upgrading" at Zanata translation defect. is this Present Progre...
Status: NEW
Product: Fedora
Classification: Fedora
Component: dnf (Show other bugs)
Unspecified Unspecified
low Severity unspecified
: ---
: ---
Assigned To: rpm-software-management
Fedora Extras Quality Assurance
: i18n, Triaged
Depends On:
  Show dependency treegraph
Reported: 2016-02-07 05:42 EST by ooyama yosiyuki
Modified: 2017-02-28 04:53 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description ooyama yosiyuki 2016-02-07 05:42:28 EST
Description of problem:  

DNF Massage translation defect. The message "Upgrading" in DNF is Present participle or Gerund.

When I translate DNF message from English to Japanese at Zanata, the "Upgrading" is used as Present participle. But at another scene ,"Upgrading" is used as Gerund.

In English language grammar, the word of Present participle is same string to Gerund.
But in Japanese grammar, It is not same string. 
In the Japanese language grammar, the word of Present participle string is different from Gerund string.

Therefore, It is different mean between Present participle and Gerund. But both scene come from at same message of Zanata message ID.

In Japanese Zanata,  both scene message ID is 
#28; Refs: ../dnf/yum/ ../dnf/cli/

At my Japanese language, If I translate as Present participle, then at another scean which "Upgrading" is used as Gerund the sentence will cause inconsistent. If I translate as Gerund, then at another scean the another sentence Which "Upgrading" is used as Present participle will cause inconsistent.

Therefore, at the time of the translation, I can not distinguish the difference of meaning in Japanese. Therefore, the sentence will cause inconsistent.

Please split "Upgrading" message ID to two message IDs.
One ID is to as Present participle, another ID is to as Gerund.

and "Downloading" message string, There is a similar problem,too.
Please split this message ID to two IDs. too.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 ooyama yosiyuki 2016-02-07 05:53:32 EST
In addition to the above, 
"Installing" string, There is similar grammar problem, too.
Please split this message ID to two IDs. too.

And "Reinstalling" string, There is similar grammar problem, too.
Please split this message ID to two IDs. too.
Comment 2 ooyama yosiyuki 2016-02-08 01:19:13 EST
And "Removing" string, There is similar grammar problem, too.
Please split this message ID to two IDs. too.
Comment 3 Honza Silhan 2016-02-08 08:13:31 EST
Would just splitting fix the problem? How can translator of eng string know which tense it should be? Can you please propose your solution via pull request [1]? I though about renaming "Installing" and so on in transaction summary to "To be installed", etc. But then the wording would be too complicated.

Comment 4 ooyama yosiyuki 2016-02-08 22:28:15 EST
The reason that I have reported to this bugzilla is,
Because I was redirected from the DNF official bug-report link "".

In this DNF official page, The link message "File a bug with" in the chapter "New feature request" redirects me to this Red-Hat Bugzilla page.
Comment 5 ooyama yosiyuki 2016-02-08 22:41:46 EST
Already I have reported this problem to Fedora-translation Japanese-team. 
And I was suggested by a team member to report this bug to DNF Official Site etc.

Therefore , I looked at DNF official Website.
And I was redirected from DNF Website to RedHat Bugzilla here.
Comment 6 ooyama yosiyuki 2016-02-08 23:01:34 EST
Sorry, mistake in writing.

redirected ->  transferred

That is, I was transferred from DNF site to this Bugzilla page.
Comment 7 ooyama yosiyuki 2016-02-09 22:01:24 EST
Thank you, Mr.Jan Silhan.

Is your suggestion about "To be installed" is alike next example ?

 Package                   Arch   Version                         Repository
To be Installed:
 kernel                    x86_64 4.3.5-300.fc23                  updates  53 k
 kernel-core               x86_64 4.3.5-300.fc23                  updates  20 M
 kernel-modules            x86_64 4.3.5-300.fc23                  updates  18 M
To be Upgraded:
 createrepo_c              x86_64 0.10.0-2.fc23                   updates  76 k
 createrepo_c-libs         x86_64 0.10.0-2.fc23                   updates  95 k

Transaction Summary


Transaction test succeeded.
Running transaction
  Upgrading   : selinux-policy-3.13.1-158.4.fc23.noarch                    1/55 
  Upgrading   : linux-firmware-20160204-61.git91d5dd13.fc23.noarch         2/55 
  Installing  : kernel-core-4.3.5-300.fc23.x86_64                          3/55 
  Installing  : kernel-modules-4.3.5-300.fc23.x86_64                       4/55  

If the thing that you say is alike this example, I agree your idea.

By the way, Sorry, now I don't know How to use GitHub. because I have never used GitHub and Pull-Request.
Comment 8 Fedora Admin XMLRPC Client 2016-07-08 05:39:24 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 9 Fedora End Of Life 2016-11-24 10:26:15 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 10 Fedora End Of Life 2017-02-28 04:53:54 EST
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

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