Bug 73646
Summary: | Illegal control character in autorun message | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Christian Rose <menthos> |
Component: | autorun | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | goeran |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-30 14:07:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christian Rose
2002-09-07 18:56:31 UTC
^K should be there... libc info page for argp: A two part documentation string (in the variable DOC), which allows documentation both before and after the options; the two parts of DOC are separated by a vertical-tab character ('\v', or '\013'). In the source code there is the string "\v", but for the .po file generation, it seemed to be translated.. In any case, placing this type of control characters inside messages marked for gettext translation is very broken. It's easy to miss this type of control character, it's easy to "translate" it into something else, and there's no point in having this control character marked for translation in the first place, since it presumably shouldn't be translated per se. My proposed solution is to split this message into several smaller ones (one per paragraph), which wouldn't just make this large message easier to translate but also would allow the control character to be moved outside of the gettext call. It could be tricky to split this message into smaller parts since it probably is a static, compile-time assigned structure. But it would help the translator if a comment mentioned that the ^K is indeed intentional and should be kept at that position. There is some way to format comments so that gettext forwards them to the po files; I keep forgetting the details though. though not critical, I will change this in the next version and keep that in mind... fixed in 3.5 |