[Bug 517595] New: "Funny" characters in openSUSE license agreement
http://bugzilla.novell.com/show_bug.cgi?id=517595 Summary: "Funny" characters in openSUSE license agreement Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke@novell.com ReportedBy: gp@novell.com QAContact: ke@novell.com CC: jw@novell.com, michl@novell.com Found By: Product Management This is what I saw with "zypper up" on a system running, ahem, ISO-8859-1 for the particular user: the exception of certain files containing the âopenSUSEâ trademark discussed below, the license terms for the components permit you to copy and redistribute the component. I assume there are some special quotes around openSUSE here? Can we just use regular quotes? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c1 Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com AssignedTo|ke@novell.com |coolo@novell.com --- Comment #1 from Karl Eichwalder <ke@novell.com> 2009-06-29 23:29:20 MDT --- Wondering why zypper is not able to transliterate basic UTF-8 letters on the fly, though. gettext knows about this and iconv/libiconv, too (IIRC, it is the //translit switch). Lately, YaST was also affected and probably still is... This "bug" occurs again and again. The guys who packages the license file probably must check the file for "bad" content and convert to ASCII. Which is not reliable as long as we do not use a file format with embedded encoding information (say, XML or .po). BTW, the documentation department is not involve in the process "all around the license file". It is written by legal (I guess), then approved by PM and the project manager and then packaged by a packager resp. by the autobuild team, IIRC. Assigning to coolo to take a decision. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User jw@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c2 --- Comment #2 from Juergen Weigert <jw@novell.com> 2009-06-30 06:39:04 MDT --- On behalf of the documentation department, I can provide a script that filters out all funny characters, and check for lines longer than 80 chars, and similar helpful transformations, if this is required. Usually, the issue with plain text files is, that no part of the system knows the exact encoding that a document is in, or should be in. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c3 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Documentation |libzypp AssignedTo|coolo@novell.com |zypp-maintainers@forge.prov | |o.novell.com QAContact|ke@novell.com |qa@suse.de --- Comment #3 from Stephan Kulow <coolo@novell.com> 2009-07-13 06:13:23 MDT --- I think zypper has to learn to transliterate - opensuse licenses are not the only ones to be displayed -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c4 Karl Eichwalder <ke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ke@novell.com --- Comment #4 from Karl Eichwalder <ke@novell.com> 2009-07-13 06:42:23 MDT --- Here is how you can do this with the external iconv command: If you want to ensure that it is all ASCII, convert back and forth using iconv: iconv -f UTF-8 -t ASCII | iconv -f ASCII -t UTF-8 If you are interested in filtering out resp. replacing "funny" chars, use iconv: echo “help™” | LANG=en_US iconv -f UTF-8 -t ascii//translit ==> "help(TM)" For foreign texts: echo “hülfe™” | LANG=de_DE iconv -f UTF-8 -t ascii//translit ==> "huelfe(TM)" Using the library is probably possible, too. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c5 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED AssignedTo|zypp-maintainers@forge.prov |jkupec@novell.com |o.novell.com | --- Comment #5 from Ján Kupec <jkupec@novell.com> 2009-07-13 08:34:30 MDT --- Thanx. This might also be a dupe of 309293. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c6 --- Comment #6 from Ján Kupec <jkupec@novell.com> 2009-07-13 08:34:57 MDT --- bug 309293 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User gp@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c7 --- Comment #7 from Gerald Pfeifer <gp@novell.com> 2009-07-13 08:40:18 MDT --- Yes, and no. One approach to this concrete item would be adjusting the openSUSE license agreement. That should be easy, and reduce time pressure to address the full blown problem a bit (though one could also argue this as a drawback of that approach -- 309293 was opened 2007-09-10). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=517595 User ke@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=517595#c8 --- Comment #8 from Karl Eichwalder <ke@novell.com> 2009-07-15 04:47:24 MDT --- bug 514309 is related. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c10 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |libzypp Version|Factory |Final Product|openSUSE 11.2 |openSUSE 13.1 --- Comment #10 from Karl Eichwalder <ke@suse.com> 2013-11-12 11:46:24 CET --- it is still an open issue on 13.1. yast (ncurses ui) displays it wrongly. adjusting version info. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |YaST2 AssignedTo|zypp-maintainers@forge.prov |gs@suse.com |o.novell.com | QAContact|qa-bugs@suse.de |jsrain@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c11 --- Comment #11 from Gabriele Mohr <gs@suse.com> 2013-11-28 12:47:08 UTC --- On text mode console and during installtion only chars can be displayed which are available in font set (check with 'showconsolefont'). Copyright sign is available here but only one kind of "" and the license file contains 2 different types of "". But the problem is not only with ncurses UI. Also 'zypper' started in xterm shows the license and there the problem is also not having all chars available, see screenshot, here the Copyright is missing. I recommend to use only chars which are available in font on console and X terminal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c12 --- Comment #12 from Gabriele Mohr <gs@suse.com> 2013-11-28 12:48:17 UTC --- Created an attachment (id=569535) --> (http://bugzilla.novell.com/attachment.cgi?id=569535) license in zypper -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c13 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |ke@suse.com --- Comment #13 from Gabriele Mohr <gs@suse.com> 2013-11-28 12:49:25 UTC --- Karl, what's your opinion. Does this make sense? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c14 --- Comment #14 from Juergen Weigert <jw@suse.com> 2013-12-03 20:11:31 UTC --- As long as we live with limited fonts, zypper and yast cannot rely on UTF-8. They should play safe and use the suggested iconv commands, or eqivalents. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c15 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|ke@suse.com | --- Comment #15 from Karl Eichwalder <ke@suse.com> 2013-12-04 10:16:42 CET --- (In reply to comment #14)
As long as we live with limited fonts, zypper and yast cannot rely on UTF-8. They should play safe and use the suggested iconv commands, or eqivalents.
Yes, I think Jan also agreed with this (see comment 4 and comment 5). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c16 --- Comment #16 from Gabriele Mohr <gs@suse.com> 2013-12-05 08:32:55 UTC --- YaST and zypper rely on UTF-8 since 2003. All code has to be UTF-8 encoded. Problem here is not about UTF-8 but about chars not available in font set. As written in comment #11, the license contains 2 different types of "", one type isn't available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c17 --- Comment #17 from Gabriele Mohr <gs@suse.com> 2013-12-05 08:39:50 UTC --- (In reply to comment #16)
YaST and zypper rely on UTF-8 since 2003. All code has to be UTF-8 encoded. Of course 'all text'... Problem here is not about UTF-8 but about chars not available in font set. As written in comment #11, the license contains 2 different types of "", one type isn't available. And the Copyright is not displayed correctly in zypper (screenshot comment #12). Solution for both cannot be done in Ncurses UI.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c18 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@suse.com --- Comment #18 from Lukas Ocilka <locilka@suse.com> 2013-12-05 08:58:27 UTC --- Let's put it in a different way - UTF-8 is required for Yast. The rest of strings is also in UTF-8 (translations). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c19 --- Comment #19 from Lukas Ocilka <locilka@suse.com> 2013-12-05 08:59:49 UTC --- See https://bugzilla.novell.com/show_bug.cgi?id=309293#c10 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c20 --- Comment #20 from Karl Eichwalder <ke@suse.com> 2013-12-05 10:58:26 CET --- If you use gettext properly, (In reply to comment #18)
Let's put it in a different way - UTF-8 is required for Yast. The rest of strings is also in UTF-8 (translations).
Agreed. But the problem is that the tools do not seem to respect the capabilities of the output device. But gettext supports it: https://www.gnu.org/software/libc/manual/html_node/Charset-conversion-in-get... Also see Kulow's comment (c#3). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
From man bind_textdomain_codeset: By default, the gettext family of functions returns translated messages in the locale's character encoding, which can be retrieved as nl_lang- info(CODESET). The need for calling bind_textdomain_codeset arises for
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c21 --- Comment #21 from Gabriele Mohr <gs@suse.com> 2013-12-05 10:58:13 UTC --- The description in link above is misleading. The "desired output character set" is not related to the font but to the character encoding, e.g. UTF-8, UTF-16 or ASCII. The function "bind_textdomain_codeset (const char * domainname, const char * codeset)" with 'codeset' set to "utf8" is called in libyui-ncurses (and same way in libyui-qt). pro- grams which store strings in a locale independent way (e.g. UTF-8) and want to avoid an extra character set conversion on the returned translated messages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c22 --- Comment #22 from Gabriele Mohr <gs@suse.com> 2013-12-05 12:31:56 UTC --- In fact 'bind_textdomain_codeset' is not called any longer in libyui-ncurses but in yast2-core (YCode.cc) with codeset set to "UTF-8". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c23 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |WONTFIX --- Comment #23 from Gabriele Mohr <gs@suse.com> 2013-12-05 13:53:48 UTC --- I don't see a way for solution on YaST side. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c24 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|WONTFIX | --- Comment #24 from Gerald Pfeifer <gp@suse.com> 2014-02-16 21:33:46 CET --- This report wasn't filed again YaST(In reply to comment #23)
I don't see a way for solution on YaST side.
This report wasn't filed against YaST, but zypper. Apart from that, can't there be a simple check of whether a character is representable in the current font and transliterate it to ASCII or whatever (per comment #4 for example) in case it's not? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c25 --- Comment #25 from Juergen Weigert <jw@suse.com> 2014-02-17 10:26:02 UTC --- A more recent iconv (from glibc-2.17-4.7.1) is worse. I'd suggest not to use the code from comment #4 blindly: cd /etc/YaST2/licenses/base LANG=de_DE iconv -f UTF-8 -t ascii//translit < license.de.txt > /tmp/l.detxt diff -u license.de.txt /tmp/l.de.txt .. jeweiligen Komponente. Mit Ausnahme bestimmter Dateien, die die -nachstehend erläuterte Marke „openSUSE“ enthalten, ermöglichen es +nachstehend erlauterte Marke ,,openSUSE" enthalten, ermoglichen es Ihnen die Lizenzbedingungen zu den Komponenten, die jeweilige .. ae and oe umlaut transliteration fails. Converting opening quotes into two chars and closing quotes into one char is bad. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED AssignedTo|gs@suse.com |jw@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c27 --- Comment #27 from Juergen Weigert <jw@suse.com> 2014-02-18 11:19:14 UTC --- Gabi, do we have a 'definition' of which characters are safe/unsafe? Currently I am aware of - odd quotation marks, - bullets and hyphens. rpm -qf /etc/YaST2/licenses/base/license.txt file /etc/YaST2/licenses/base/license.txt is not owned by any package Where should we submit fixed license texts? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c Juergen Weigert <jw@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |gs@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c29 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|gs@suse.com | --- Comment #29 from Gabriele Mohr <gs@suse.com> 2014-02-27 15:22:02 UTC --- (In reply to comment #27)
Gabi, do we have a 'definition' of which characters are safe/unsafe?
Currently I am aware of - odd quotation marks, - bullets and hyphens.
I don't have a definition. It seems Karl found a solution (bnc #849449, comment #8).
rpm -qf /etc/YaST2/licenses/base/license.txt file /etc/YaST2/licenses/base/license.txt is not owned by any package
Where should we submit fixed license texts?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=517595 https://bugzilla.novell.com/show_bug.cgi?id=517595#c30 Juergen Weigert <jw@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |WONTFIX --- Comment #30 from Juergen Weigert <jw@suse.com> 2014-02-27 15:41:46 UTC --- Gabi, I agree that Karls manual solution is adequate. Given that an automated solution is aparently hard, I'd suggest to close this as wontfix. The downside is that we rely on QA (from PMs and Beta testers) to catch individual cases. Gerald, please reopen, if you disagree. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com