|
Bugzilla – Full Text Bug Listing |
| Summary: | Releasenotes contain odd characters | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Juergen Weigert <jw> |
| Component: | Release Notes | Assignee: | Karl Eichwalder <ke> |
| Status: | RESOLVED FIXED | QA Contact: | Stephan Kulow <coolo> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | gs, ke, maintenance |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 852179 | ||
| Attachments: | screenshot showing replacement chars | ||
From my technical opensuse POV, this is not a bug. At least, not a bug with the text file. (If you'd view a Chinese translation file, you'd see nothing but question marks...) Of course, yast could work around the "problem" and - if it runs in a C locale environment - it could transliterate the input before displaying it: iconv --from-code=UTF-8 --to-code=ascii//TRANSLIT \ /usr/share/doc/release-notes/openSUSE/RELEASE-NOTES.en.txt gettext does similar things for translations. Since all the .txt files work perfectly fine if you'd view them with YaST in a xterm, I would not like to change these files at package build time... The inverted ? on console indicates that this char isn't available in console font. On the other hand the Copyright sign is not available in an xterm. I recommend to use only chars available in console and X font in the *.txt files for text mode. For me a good example is /usr/share/doc/release-notes/openSUSE/fdl.txt. The problem is also with openSUSE license (see bnc #517595). (In reply to comment #1) > From my technical opensuse POV, this is not a bug. At least, not a bug with > the text file. (If you'd view a Chinese translation file, you'd see nothing > but question marks...) > > Of course, yast could work around the "problem" and - if it runs in a C locale > environment - it could transliterate the input before displaying it: > > iconv --from-code=UTF-8 --to-code=ascii//TRANSLIT \ > /usr/share/doc/release-notes/openSUSE/RELEASE-NOTES.en.txt > > gettext does similar things for translations. > > Since all the .txt files work perfectly fine if you'd view them with YaST in a > xterm, I would not like to change these files at package build time... The Copyright sign is not displayed correctly with 'zypper' or even 'vi'. Karl, what do you think about my proposal not to use chars in question at all? (In reply to comment #5) > Karl, what do you think about my proposal not to use chars in question at all? This will not work for many a lot languages that we ship with openSUSE. Proper i18n implementation is needed. It should be possible to check which features the output device supports and then apply appropriate transliteration commands. Of course, nobody expects that you can read Chinese text in a Czech environment ("cs_CZ") on the text console. If I'd transliterate German .txt files to ascii (ae, oe, ue instead of proper umlauts), it would look stupid in an xterm. Thus, the transliteration must happen at display time, IMO. YaST and zypper rely on UTF-8, all text has to be UTF-8 encoded (Ncurses UI was adapted in 2003). It's not about transliterate .txt files to ASCII and not displaying Umlauts. It's only about chars not available in font set. Umlauts will be displayed properly on console and X terminal, they are available in font for german language and also chars e.g. for Czech which are in Czech font set. Adding code to check chars at display to Ncurses UI doesn't help for zypper. Ok, I'll try to eliminate the fancy quotes from the .txt files (with 'sed' or a similar tool). Fixed in SVN. openSUSE-RU-2013:1887-1: An update that has four recommended fixes can now be installed. Category: recommended (low) Bug References: 849449,850058,851083,851588 CVE References: Sources used: openSUSE 13.1 (src): release-notes-openSUSE-13.1.9-29.1 It was only partially fixed. 'make' must be called from a UTF-8 environment. Another update is required, please (plus more translation updates): release-notes-openSUSE> osc sr -m.10 home:keichwa:branches:openSUSE:13.1:Update release-notes-openSUSE openSUSE:13.1:Update WARNING: WARNING: Project does not accept submit request, request to open a NEW maintenance incident instead WARNING: created request id Request: #213148 maintenance_incident: home:keichwa:branches:openSUSE:13.1:Update/release-notes-openSUSE -> openSUSE:Maintenance (release in openSUSE:13.1:Update) Message: .10 State: new 2014-01-08T12:41:30 keichwa Comment: <no comment> openSUSE-RU-2014:0066-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 849449 CVE References: Sources used: openSUSE 13.1 (src): release-notes-openSUSE-13.1.10-33.1 |
Created attachment 566551 [details] screenshot showing replacement chars The console font used when running yast as root from tty1 uses the inverted question mark as a replacement character for quotation marks.