| Summary: | publican and publican-doc should include translations | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jibecfed <jean-baptiste> |
| Component: | publican | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | jfearn, me, mmcallis, rlandman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-20 19:55:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
jibecfed
2016-04-11 22:29:47 UTC
IIRC we deliberately exclude fuzzy translations upstream as it's apparently "not the right thing to do" ... what do you think Rudi? FYI they are both easy changes, just add --showfuzzy to the publican build calls in the spec file and add ", fuzzy => 1" to the "Locale::Msgfmt::msgfmt" call in Build.PL. Also I note there are two docs packages publican-doc and publican-releasenotes, should we combine them so installing t publican-doc, or should we ship the release notes in the main package? as a translator, I agree with excluding fuzzy strings. The strings to include are only "Translated" or "Validated". I know publican crash if there is fuzzy strings, but I'm afraid you'll have to correct this in an other way : a script that clean po files. Publican does not crash if there are fuzzy strings, which is why there are options to enable using them. The logic for fuzzy strings is that if there are any fuzzy strings in a translation then the whole translation get's dropped. Using the options mentioned in comment one will get the behavior you are requesting. Well too late for F24 :( It's i place for the next publican release though. To ssh://git.fedorahosted.org/git/publican.git f0773ea..d98d4c6 devel -> devel [jfearn@obelisk publican]$ 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. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |