[Bug 361270] New: We should try to get rid of SuSEconfig.groff
https://bugzilla.novell.com/show_bug.cgi?id=361270 Summary: We should try to get rid of SuSEconfig.groff Product: openSUSE 11.0 Version: Alpha 2 Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mfabian@novell.com QAContact: qa@suse.de Found By: Development We should try to get rid of SuSEconfig.groff. -- 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=361270 Mike Fabian <mfabian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msvec@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |mfabian@novell.com Status|NEW |ASSIGNED -- 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=361270 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=361270#c1 --- Comment #1 from Mike Fabian <mfabian@novell.com> 2008-02-12 14:29:06 MST ---
I wonder, is it on purpose our groff is not at 1.19.2?
Support for Chinese and Japanese. Our groff 1.18.1.1 package contains a patch (from Debian) which adds Japanese and Chinese support. This patch is a ugly hack and was therefore not accepted upstream. And it has not been ported to groff 1.19.x. Upstream they say that they want to implement proper Unicode support, which is a good idea. And they have made some progress during the last years. Nevertheless, as far as I know, groff 1.19.2 still doesn’t support Japanese and Chinese after all these years.
I'm curious if we would be able to get rid of SuSEconfig.groff finally :)
That will vanish in an update because it is only used to set the paper size in a Debian specific way which comes "bundled" with the Japanese/Chinese patch from Debian. Upstream the papersize is not set that way, i.e. if we manage to update to 1.19.2 and drop the Debian patch, we would get rid of that funny way setting the paper size. But we should not loose Japanese and Chinese support when upgrading, that makes it difficult. -- 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=361270 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=361270#c2 --- Comment #2 from Mike Fabian <mfabian@novell.com> 2008-02-12 14:34:13 MST --- Created an attachment (id=194553) --> (https://bugzilla.novell.com/attachment.cgi?id=194553) gr.diff Patch suggested by Michal Svec. -- 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=361270 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=361270#c3 --- Comment #3 from Mike Fabian <mfabian@novell.com> 2008-02-12 14:54:24 MST --- I tried to test how groff reacts to /etc/papersize to make sure that it still works after applying something like Michal Svec’s patch. To my surprise I found that /etc/papersize already seems to be ignored. At least the command line LANG=en_US.UTF-8 man -Tps bash > /tmp/ttt.ps produces the same PostScript output no matter whether I put “letter” or “a4” into /etc/papersize. -- 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=361270 User msvec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=361270#c4 --- Comment #4 from Michal Svec <msvec@novell.com> 2008-02-21 07:57:50 MST --- That is interesting, does it mean we could get rid of the SuSEconfig.groff right away? -- 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=361270 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=361270#c5 --- Comment #5 from Mike Fabian <mfabian@novell.com> 2008-02-21 08:03:05 MST --- I think so, throwing away SuSEconfig.groff right now without fixing anything in groff wouldn’t make it any more broken than it already is, as far as I can see. I don’t know whether I should spend some effort to make the papersize stuff in groff work at all. At the moment I am busy with other stuff, i.e. maybe I just throw away t he SuSEconfig.groff script now and try to make the papersize handling work correctly later. -- 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=361270 Mike Fabian <mfabian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mfabian@novell.com |hvogel@novell.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=361270 User hvogel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=361270#c6 Hendrik Vogelsang <hvogel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #6 from Hendrik Vogelsang <hvogel@novell.com> 2009-03-05 09:59:33 MST --- papersize in groff wont be fixed anymore by us so i close this -- 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