Auslaenderpolitik

Lese selbst: http://www.mjoelnirsseite.de/2100.htm ___ Bug-groff mailing list Bug-groff@gnu.org http://lists.gnu.org/mailman/listinfo/bug-groff

Tuerkei in die EU

GEWALTEXZESS: http://www.spiegel.de/politik/ausland/0,1518,345203,00.html Politiker zerreißt Menschenrechtsbericht: http://www.spiegel.de/politik/ausland/0,1518,325983,00.html Schily = Hitler http://www.spiegel.de/politik/deutschland/0,1518,345929,00.html Schily wehrt sich gegen Hitler-Vergleich

D0ct0r rec0mmendati0ns

WXftsVe0BjTWhoN0VdohaBCmeO618goa8Y9CyZWhGDOxj7YzlSmejUlaJbn66j27qYPsj3HqdgU6 Qzp5WY5wA4cqmpw1PeczeOvriKgXh5CtSiLvYfXiqcYZXT3clLnkDGGjFKWEKAmnVPybnRw0CJQXcp3 THAt82skdcJ9qSFMAu1Vym37E6ELmztRU5kc8z0easmxgVkJ4GSg5Mq0FM52Vbi9cIA0u3 HVtaKkCvBpwwdJZVHTAxiQoPHixLDmAjE6QjzMCgowJMyyvckugEwMFTHvefT

[bug #40967] numerous minor documentation fixes

Follow-up Comment #6, bug #40967 (project groff): OK. Then this bug should be left open to indicate that there is still work to be done. Although I'm the submitter, there does not appear to be a way for me to reopen it. ___ Reply to this

[bug #42191] -me macro bug involving word with an umlaut

URL: Summary: -me macro bug involving word with an umlaut Project: GNU troff Submitted by: barx Submitted on: Thu 24 Apr 2014 06:18:50 PM CDT Severity: 3 - Normal Item Gr

[bug #40967] numerous minor documentation fixes

Follow-up Comment #4, bug #40967 (project groff): I note that one of the non-Bjarni patches in this list was not applied: patch: resubmitted -me documentation fixes 12 Nov 2013 01:19:46 -0600 http://lists.gnu.org/archive/html/bug-groff/2013-11/msg7.html Are there problems with this patch tha

[bug #42217] -me macro .(b block has incorrect vertical spacing

URL: Summary: -me macro .(b block has incorrect vertical spacing Project: GNU troff Submitted by: barx Submitted on: Sun 27 Apr 2014 08:50:14 PM CDT Severity: 3 - Normal

[bug #42503] Illogical precedence of .hw over .hy

URL: Summary: Illogical precedence of .hw over .hy Project: GNU troff Submitted by: barx Submitted on: Tue 03 Jun 2014 07:33:36 PM CDT Severity: 3 - Normal Item Group: No

[bug #42515] clean up an-old.tmac namespace

URL: Summary: clean up an-old.tmac namespace Project: GNU troff Submitted by: barx Submitted on: Fri 06 Jun 2014 05:03:10 AM CDT Severity: 3 - Normal Item Group: None

[bug #43239] broken interaction between line numbering and diversions

URL: Summary: broken interaction between line numbering and diversions Project: GNU troff Submitted by: barx Submitted on: Tue 16 Sep 2014 08:54:19 PM CDT Severity: 3 - Normal

[bug #43306] -me macro .(c block misaligned

URL: Summary: -me macro .(c block misaligned Project: GNU troff Submitted by: barx Submitted on: Sat 27 Sep 2014 02:35:22 AM CDT Severity: 3 - Normal Item Group: None

[bug #44235] UPGRADE: provide a way to redefine an existing symbol in a specific font

URL: Summary: UPGRADE: provide a way to redefine an existing symbol in a specific font Project: GNU troff Submitted by: barx Submitted on: Fri 13 Feb 2015 12:36:00 AM CST Severity: 3 -

[bug #44244] UPGRADE: Let document define kern pairs, including between characters in different fonts

URL: Summary: UPGRADE: Let document define kern pairs, including between characters in different fonts Project: GNU troff Submitted by: barx Submitted on: Fri 13 Feb 2015 05:03:21 PM CST

[bug #46319] errors in info pages

URL: Summary: errors in info pages Project: GNU troff Submitted by: barx Submitted on: Thu 29 Oct 2015 12:22:16 AM CDT Severity: 3 - Normal Item Group: None

[bug #46327] groff should fail rather than producing invalid PostScript code

URL: Summary: groff should fail rather than producing invalid PostScript code Project: GNU troff Submitted by: barx Submitted on: Thu 29 Oct 2015 05:07:10 PM CDT Severity: 3 - Normal

[bug #46327] groff should fail rather than producing invalid PostScript code

Follow-up Comment #2, bug #46327 (project groff): I'm using groff 1.22.2, the latest available for the x86 architecture under Gentoo Linux. Adding the -ww flag does not have any visible effect: no new warning is produced, the exit status is unchanged, and the PostScript output is identical (excep

[bug #46327] groff should fail rather than producing invalid PostScript code

Follow-up Comment #4, bug #46327 (project groff): Thank you for looking into it and providing such a lucid explanation. ___ Reply to this item at: ___ M

[bug #46319] errors in info pages

Follow-up Comment #1, bug #46319 (project groff): I've attached a patch to fix the described problems. This patch also fixes - examples in the section about the \, e, and E escapes where the given code did not produce the documented result - a few typos and grammar and punctuation errors Ple

[bug #42503] Illogical precedence of .hw over .hy

Follow-up Comment #1, bug #42503 (project groff): Groff also does not obey the .hy value for any words in /usr/share/groff/current/tmac/hyphenex.us. An example to illustrate: .ll 1i Visit yonder arboretum. .br Visit yonder archipelago. .br .hy 8 "should prevent brea

[bug #42503] Illogical precedence of .hw over .hy

Follow-up Comment #2, bug #42503 (project groff): (I don't seem to have the ability to change the title of this bug, but the present title is inaccurate, since the bug doesn't depend on the user using .hw at all.) ___ Reply to this item at:

[bug #46914] .ce sometimes ignores right margin

URL: Summary: .ce sometimes ignores right margin Project: GNU troff Submitted by: barx Submitted on: Sat 16 Jan 2016 07:06:09 PM CST Severity: 3 - Normal Item Group: Inco

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

URL: Summary: .PSPIC macro at bottom of page causes unwarranted page break Project: GNU troff Submitted by: barx Submitted on: Sun 09 Apr 2017 02:38:54 PM CDT Severity: 3 - Normal

[bug #50778] .ta documentation does not match behavior

URL: Summary: .ta documentation does not match behavior Project: GNU troff Submitted by: barx Submitted on: Mon 10 Apr 2017 07:35:42 AM CDT Severity: 3 - Normal Item Grou

[bug #42503] Illogical precedence of .hw over .hy

Follow-up Comment #3, bug #42503 (project groff): Additionally, a user asking groff not to split words by leaving only two characters on a line might reasonably expect this to include words already containing hyphens. However, groff does not honor this restriction, either: .\" don't hyphenate th

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

Follow-up Comment #5, bug #50770 (project groff): Thank you both for your work in analyzing this! Because this behavior is undocumented, I submit that we can change it in a way that typographically improves the output. Its current behavior is subpar whether there is a caption or not. If the ima

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

Follow-up Comment #7, bug #50770 (project groff): > The problem with changing it is that it breaks backward > compatibility, which is important for software which has > been around for a long time. A document created 15 years > ago should render the same now as it did then. I do not believe that

[bug #50770] .PSPIC macro at bottom of page causes unwarranted page break

Follow-up Comment #9, bug #50770 (project groff): > Yes, so the maximum amount of usable space which > is lost, is 1v. No, the maximum amount of usable space that is lost (for any size graphic) is the height of the graphic. Consider three cases, with a 10cm x 10cm graphic as an example. 1. At t

[bug #42191] -me macro bug involving word with an umlaut

Follow-up Comment #1, bug #42191 (project groff): Is there anything that should prevent this patch from being applied? It solves a legitimate problem that results in illegible output, and it has caused no problems that I've noticed since first applying it in 2011. I've attached it to this bug re

[bug #53196] .hy values 4 and 8 ignored for some words

URL: Summary: .hy values 4 and 8 ignored for some words Project: GNU troff Submitted by: barx Submitted on: Tue 20 Feb 2018 10:55:57 PM CST Category: None Severity: 3 -

[bug #42503] Illogical precedence of .hw over .hy

Follow-up Comment #4, bug #42503 (project groff): Because this bug's description is spread over multiple comments, its title is obsolete, and this bug tracker seemingly lacks the ability to edit a bug title, I have consolidated the various comments here and placed them under a more accurate bug ti

[bug #40967] numerous minor documentation fixes

Follow-up Comment #10, bug #40967 (project groff): As far as I know, only the patch mentioned in comment #4 hasn't been applied. I'm attaching an updated version of it that works with the latest code in git. (file #43378) ___ Additional It

[bug #53196] .hy values 4 and 8 ignored for some words

Follow-up Comment #2, bug #53196 (project groff): > The file `hyphenex.us' is read with the `.hpfa' > request, and all data read in with this request > should indeed be subject to `.hy'. Yes, this is the core bug. The other cases are side issues (perhaps I should have separated them into their o

[bug #53196] .hy values 4 and 8 ignored for some words

Follow-up Comment #4, bug #53196 (project groff): > 3) The '.hy 8' works in 'nroff 1.22.3' (Debian 1.22.3-10) > but not in version 1.22.3.real.441-d6ec5 Then this is a regression that needs to be addressed. > 4) The values 4 and 8 are incompatible with the current > method of hyphenation and mak

[bug #53243] regression: .hy not working in latest groff build

URL: Summary: regression: .hy not working in latest groff build Project: GNU troff Submitted by: barx Submitted on: Tue 27 Feb 2018 07:33:52 PM CST Category: None Sever

[bug #53196] .hy values 4 and 8 ignored for some words

Follow-up Comment #6, bug #53196 (project groff): Because the regression Bjarni reported in comment #3 is a separate issue from the primary one in this bug report, I've opened bug #53243 for it. Further comments about overall use of .hy 4 and 8 should go there. To respond to comment #5: I agree

[bug #53243] regression: .hy not working in latest groff build

Follow-up Comment #2, bug #53243 (project groff): Yes, it works now. Thank you! ___ Reply to this item at: ___ Message sent via/by Savannah http://sa

[bug #53196] .hy values 4 and 8 ignored for hyphenation exceptions read with .hpf or .hpfa

Follow-up Comment #8, bug #53196 (project groff): Yes, I confirm that the core issue and the documentation issue (elucidated in comment #2) have both been fixed. Thank you! ___ Reply to this item at:

[bug #53837] Feature request: mechanism to control .hw/.hy interaction

URL: Summary: Feature request: mechanism to control .hw/.hy interaction Project: GNU troff Submitted by: barx Submitted on: Fri 04 May 2018 02:44:27 PM CDT Category: Core

[bug #53413] [PATCH] Add hyphenation patterns to use with US and hy=48

Follow-up Comment #6, bug #53413 (project groff): > And `generally' using `.hy 48' is a bad idea. Values of > `.hy' are always bound to the currently selected hyphenation > patterns. Yes, but the entire reason .hy 48 produces erroneous output is that the hyphenation patterns were not crafted with

[bug #53413] [PATCH] Add hyphenation patterns to use with US and hy=48

Follow-up Comment #8, bug #53413 (project groff): > It's outside of groff's scope to decide that since it is > meta information bound to a given language. Well, yes and no. Looking at the bigger picture: In English, a single letter is not a valid hyphenation breakpoint, even if it is a syllable

[bug #54101] documentation for .ss either incorrect or incomplete

URL: Summary: documentation for .ss either incorrect or incomplete Project: GNU troff Submitted by: barx Submitted on: Tue 12 Jun 2018 01:46:21 AM CDT Category: Core Se

[bug #54101] documentation for .ss either incorrect or incomplete

Follow-up Comment #1, bug #54101 (project groff): The other possibility is that the documentation is correct, and groff's noncompliance with it is a bug. Modern typography does not add additional space between sentences. To emulate that, documents cannot use the default .ss setting; they must ex

[bug #54101] documentation for .ss either incorrect or incomplete

Follow-up Comment #3, bug #54101 (project groff): Hi, thanks for the followup. I'm not sure what you're asking. The discrepancy between what the info file says and what groff actually does exists no matter what any other piece of groff documentation has to say. This discrepancy is what this bug

[bug #54101] documentation for .ss either incorrect or incomplete

Follow-up Comment #5, bug #54101 (project groff): The second .ss argument has an effect: the ps file you attached definitely shows a difference between its various values. This file also further illustrates (probably better than my original example) the problem reported in this bug report: becaus

[bug #54884] doc/groff.texi: clarification of .H and .V registers

URL: Summary: doc/groff.texi: clarification of .H and .V registers Project: GNU troff Submitted by: barx Submitted on: Tue 23 Oct 2018 03:07:52 AM CDT Category: Core S

[bug #54894] doc/groff.texi: clarify \p escape

URL: Summary: doc/groff.texi: clarify \p escape Project: GNU troff Submitted by: barx Submitted on: Thu 25 Oct 2018 07:34:00 AM CDT Category: None Severity: 3 - Normal

[bug #54894] doc/groff.texi: clarify \p escape

Follow-up Comment #3, bug #54894 (project groff): That was quick! Thank you for figuring out that it needed more comprehensive wording (I'd forgotten about the non-adjustment case) and finding the man page that also needed the update. ___

[bug #54897] [PATCH] man/groff.man: correct .tm and .tm1 descriptions

URL: Summary: [PATCH] man/groff.man: correct .tm and .tm1 descriptions Project: GNU troff Submitted by: barx Submitted on: Fri 26 Oct 2018 05:47:12 AM CDT Category: None

[bug #54897] [PATCH] man/groff.man: correct .tm and .tm1 descriptions

Follow-up Comment #1, bug #54897 (project groff): Oops, the bug descriptions says man/groff.man where it means man/groff.7.man. The patch file has the correct filename. ___ Reply to this item at:

[bug #54899] [PATCH] doc/me*.me: clarifications to -me documentation

URL: Summary: [PATCH] doc/me*.me: clarifications to -me documentation Project: GNU troff Submitted by: barx Submitted on: Fri 26 Oct 2018 08:35:55 AM CDT Category: None

[bug #54910] much documentation still recommends bug-groff@gnu.org for filing bug reports

URL: Summary: much documentation still recommends bug-groff@gnu.org for filing bug reports Project: GNU troff Submitted by: barx Submitted on: Mon 29 Oct 2018 12:30:31 AM CDT Category

[bug #54915] [PATCH] doc/groff.texi: address behavior when page break occurs between .mk and .rt

URL: Summary: [PATCH] doc/groff.texi: address behavior when page break occurs between .mk and .rt Project: GNU troff Submitted by: barx Submitted on: Mon 29 Oct 2018 05:46:04 PM CDT C

[bug #40967] numerous minor documentation fixes

Follow-up Comment #12, bug #40967 (project groff): I've modified the patch again; it now only affects the files doc/meintro.me and doc/meref.me. It no longer adds text to tmac/groff_me.7.man: this man page provides a terse high-level overview, and the level of detail my previous patch added was i

[bug #40967] numerous minor documentation fixes

Follow-up Comment #14, bug #40967 (project groff): Thanks for applying this. I've emailed Grégoire about the translation. Possibly this bug report should be left open as a reminder that that still should be added. Alternately, I can open a new bug report for that, since this one covers a lot of

[bug #54958] doc/meintro_fr.me: add translation of new text in doc/meintro.me

URL: Summary: doc/meintro_fr.me: add translation of new text in doc/meintro.me Project: GNU troff Submitted by: barx Submitted on: Mon 05 Nov 2018 03:05:27 AM CST Category: None

[bug #54959] [PATCH] various minor documentation corrections

URL: Summary: [PATCH] various minor documentation corrections Project: GNU troff Submitted by: barx Submitted on: Mon 05 Nov 2018 04:18:31 AM CST Category: None Severi

[bug #54910] much documentation still recommends bug-groff@gnu.org for filing bug reports

Follow-up Comment #2, bug #54910 (project groff): Yes, your autoconf solution seems like the best fit for the man pages. I was unaware of this feature of autoconf. Being wholly unfamiliar with groff's build process, it's best that I not attempt to change any autoconf files or Makefiles, lest I b

[bug #54910] much documentation still recommends bug-groff@gnu.org for filing bug reports

Follow-up Comment #5, bug #54910 (project groff): Sounds good. For the record, Werner is OK with the change to doc/groff.texi (though I probably should have asked him to post that here so his acquiescence would be publicly visible). ___ Re

[bug #54910] much documentation still recommends bug-groff@gnu.org for filing bug reports

Follow-up Comment #6, bug #54910 (project groff): Also, for anyone browsing this bug report in the future, part of its fix is in the commit cited in comment #4, and part in commit 7908dc1dcfcb0b93fe5d35269db92702d28bc1f4. ___ Reply to this

[bug #55060] me: behavior of .ll does not match documentation

URL: Summary: me: behavior of .ll does not match documentation Project: GNU troff Submitted by: barx Submitted on: Mon 19 Nov 2018 05:25:30 PM CST Category: Macro - others

[bug #55081] me: two-column output does not work with very long page lengths

URL: Summary: me: two-column output does not work with very long page lengths Project: GNU troff Submitted by: barx Submitted on: Fri 23 Nov 2018 04:44:53 PM CST Category: Macro - oth

[bug #55060] me: behavior of .ll does not match documentation

Follow-up Comment #2, bug #55060 (project groff): > There is a translation error in the manual ("meref.me"). I don't know what this means. I'm reading meref.me in its original language, English. I have no evidence it has ever been translated out of and then back into English. Do you mean "tran

[bug #55091] stop stripping comments and spaces from installed macro packages

URL: Summary: stop stripping comments and spaces from installed macro packages Project: GNU troff Submitted by: barx Submitted on: Sat 24 Nov 2018 09:06:30 PM CST Category: Macro - ot

[bug #54958] doc/meintro_fr.me: add translation of new text in doc/meintro.me

Follow-up Comment #3, bug #54958 (project groff): I've gotten no response from the email address listed in the doc/meintro_fr.me header block. Please post here if you know of more current contact information for him, or know of someone else who could do this translation.

[bug #55124] doc/groff.texi: text about negative .pl values needs clarification

URL: Summary: doc/groff.texi: text about negative .pl values needs clarification Project: GNU troff Submitted by: barx Submitted on: Wed 28 Nov 2018 09:13:30 AM CST Category: Core

[bug #55154] .tr has undocumented and inconsistennt space-character restrictions

URL: Summary: .tr has undocumented and inconsistennt space-character restrictions Project: GNU troff Submitted by: barx Submitted on: Mon 03 Dec 2018 06:18:36 AM CST Category: None

[bug #55154] .tr has undocumented and inconsistennt space-character restrictions

Follow-up Comment #1, bug #55154 (project groff): It turns out this bug tracker has stripped the trailing spaces from my sample code, so pasting it from the bug description won't work. I've put a correct copy in an attachment. (file #45569) ___

[bug #55155] .tr is overzealous in nroff output

URL: Summary: .tr is overzealous in nroff output Project: GNU troff Submitted by: barx Submitted on: Mon 03 Dec 2018 11:50:22 AM CST Category: Device - others Severity

[bug #55155] .tr is overzealous in nroff output

Follow-up Comment #1, bug #55155 (project groff): UGH, this bug tracker is so broken. I have no idea why it munged the output of those od commands. At least the code is unmolested, so you can generate the correct output on your own system. ___

[bug #55155] .tr is overzealous in nroff output

Follow-up Comment #2, bug #55155 (project groff): It turns out commit babca15fa2d3f5ec1dd7214e31e1efc42759c220vax solved this specific instance of the problem by changing how nroff displays a dagger symbol. So the examples below do not fail in the manner described using the latest groff code and

[bug #55155] .tr is overzealous in nroff output

Follow-up Comment #3, bug #55155 (project groff): (That should read "commit babca15fa2d3f5ec1dd7214e31e1efc42759c220" -- copy/paste error) ___ Reply to this item at: ___

[bug #55124] doc/groff.texi: text about negative .pl values needs clarification

Follow-up Comment #1, bug #55124 (project groff): Regarding point (2): it's also worth considering changing .pl's behavior to the more useful option. It can't be too detrimental to back compatibility to change behavior that the documentation already admits is rather useless. Further, the current

[bug #55278] src/devices/grotty/grotty.1.man, doc/groff.texi updates

URL: Summary: src/devices/grotty/grotty.1.man, doc/groff.texi updates Project: GNU troff Submitted by: barx Submitted on: Mon 24 Dec 2018 06:26:00 PM CST Category: Core

[bug #55278] src/devices/grotty/grotty.1.man, doc/groff.texi updates

Follow-up Comment #1, bug #55278 (project groff): Side note on point 1: There is also the question of what "supporting" this actually means. One Android terminal app, for instance (specifically, JuiceSSH), renders text delineated with these escape sequences in reverse video. This is arguably ugl

[bug #55799] -a output does not heed .char definitions

URL: Summary: -a output does not heed .char definitions Project: GNU troff Submitted by: barx Submitted on: Thu 28 Feb 2019 04:31:55 PM CST Category: Core Severity: 3

[bug #55941] [PATCH] test-nroff: Create this file to accompany "test-groff"

Follow-up Comment #2, bug #55941 (project groff): This complicates matters a small amount for a small benefit. Yes, if you want to do elaborate testing, you should install the package. But if you want to do a simple test with the latest source code, perhaps to check whether some unexpected behav

[bug #55954] [PATCH] make doc/groff.texi and man/groff.7.man state that certain spaces are nonbreaking

URL: Summary: [PATCH] make doc/groff.texi and man/groff.7.man state that certain spaces are nonbreaking Project: GNU troff Submitted by: barx Submitted on: Tue 19 Mar 2019 11:37:37 AM CDT

[bug #55091] stop stripping comments and spaces from installed macro packages

Follow-up Comment #1, bug #55091 (project groff): A proposed patch to stop stripping the mdoc macro set was posted to the groff email list: http://lists.gnu.org/archive/html/groff/2019-03/msg00015.html In ensuing discussion (which thread continues at http://lists.gnu.org/archive/html/groff/2019-

[bug #42870] `.hcode' and `.hw' are limited to raw 8bit characters but should accept any characters entities.

Follow-up Comment #3, bug #42870 (project groff): To address the point raised in comment #2, init_charset_table() in src/roff/troff/input.cpp appears to be what defines the default hcode values, in particular the lines: for (int i = 0; i < 256; i++) { ... if (csalpha(i)) charset_table

[bug #56499] adjacent trap behavior undocumented and probably undesirable

URL: Summary: adjacent trap behavior undocumented and probably undesirable Project: GNU troff Submitted by: barx Submitted on: Sat 15 Jun 2019 05:54:01 AM CDT Category: Core

[bug #56500] documentation should mention trap restriction

URL: Summary: documentation should mention trap restriction Project: GNU troff Submitted by: barx Submitted on: Sat 15 Jun 2019 06:28:45 AM CDT Category: Core Severity

[bug #55278] src/devices/grotty/grotty.1.man, doc/groff.texi updates

Follow-up Comment #2, bug #55278 (project groff): Point 1 fixed in commit c105b1725cc928e225d23237f3cf1a7a5239d5bavax. Side note on point 3: According to http://en.wikipedia.org/wiki/Caret_navigation, "caret" can be a synonym for "cursor" in the context of a text editor or similar UI, but that's

[bug #57448] groff will not break a line at a hard hyphen following some letter combinations

URL: Summary: groff will not break a line at a hard hyphen following some letter combinations Project: GNU troff Submitted by: barx Submitted on: Thu 19 Dec 2019 07:16:37 AM CST Categ

[bug #57448] groff will not break a line at a hard hyphen following some letter combinations

Follow-up Comment #2, bug #57448 (project groff): How it kerns characters elsewhere on the line should have no effect on whether it is willing to break a line at a hard hyphen. If it does, this is a bug. groff will not break the line at a hyphen after these particular letter combinations. You c

[bug #57448] groff will not break a line at a hard hyphen following some letter combinations

Follow-up Comment #3, bug #57448 (project groff): But you are correct that kerning appears to be what triggers the bug. In the default font (TR), only four uppercase letters have kerning between them and a following hyphen: $ sed -n '/^kernpairs/,/^$/p' /usr/share/groff/current/font/devps/TR | g

[bug #57462] Feature request: new primitive to do underlining, strikethrough, and related markup

URL: Summary: Feature request: new primitive to do underlining, strikethrough, and related markup Project: GNU troff Submitted by: barx Submitted on: Sun 22 Dec 2019 09:25:44 AM CST C

[bug #57448] groff will not break a line at a hard hyphen following some letter combinations

Follow-up Comment #5, bug #57448 (project groff): > If the kerning in front of the hyphen is removed (with '\&'), > the expected result is there. Well, not if the expected result is for kerning and line-breaking to simultaneously work. :) If one needs a workaround, a better one is to add a zer

[bug #57498] [PATCH] nroff documentation housekeeping

URL: Summary: [PATCH] nroff documentation housekeeping Project: GNU troff Submitted by: barx Submitted on: Sun 29 Dec 2019 09:44:56 AM CST Category: Device - others Se

[bug #57506] Erroneous "slant" value in Times italic font(s) for ps device

URL: Summary: Erroneous "slant" value in Times italic font(s) for ps device Project: GNU troff Submitted by: barx Submitted on: Mon 30 Dec 2019 10:23:19 AM CST Category: Font devps

[bug #57510] not all TTY output controls simultaneously available

URL: Summary: not all TTY output controls simultaneously available Project: GNU troff Submitted by: barx Submitted on: Tue 31 Dec 2019 09:32:35 AM CST Category: Device - others

[bug #57524] gpinyin: suboptimal rendering for syllable "lue3"

URL: Summary: gpinyin: suboptimal rendering for syllable "lue3" Project: GNU troff Submitted by: barx Submitted on: Thu 02 Jan 2020 06:07:01 PM CST Category: Preprocessor - others

[bug #57538] -me macros: incorrect postscript output of macro .(b

URL: Summary: -me macros: incorrect postscript output of macro .(b Project: GNU troff Submitted by: barx Submitted on: Sat 04 Jan 2020 02:12:45 PM CST Category: Macro - others

[bug #57538] -me macros: incorrect postscript output of macro .(b

Follow-up Comment #1, bug #57538 (project groff): Further discussion about this bug, though nothing conclusive, took place on the groff email list, in the thread starting at http://lists.gnu.org/archive/html/groff/2013-03/msg00012.html ___

[bug #57538] -me macros: incorrect postscript output of macro .(b

Follow-up Comment #2, bug #57538 (project groff): Additionally, the thread mentioned in comment #1 continued for a bit off-list when Deri emailed me some PDF attachments he couldn't easily send to the list. And thanks to his work, I've been able to home in a little more on this bug. Because as i

[bug #57546] [PATCH] make \[dd] transparent for end-of-sentence detection

URL: Summary: [PATCH] make \[dd] transparent for end-of-sentence detection Project: GNU troff Submitted by: barx Submitted on: Mon 06 Jan 2020 04:22:45 PM CST Category: Core

[bug #57546] [PATCH] make \[dd] transparent for end-of-sentence detection

Follow-up Comment #1, bug #57546 (project groff): Debatably, the characters \[Fc] and \[fc] could have cflags 32 set by default as well. Arguing against: groff's defaults are tailored to English, and these characters are not used in standard English. Arguing for: these characters are closing quo

[bug #57549] [PATCH] doc/groff.texi: some .cflags default values missing

URL: Summary: [PATCH] doc/groff.texi: some .cflags default values missing Project: GNU troff Submitted by: barx Submitted on: Tue 07 Jan 2020 10:51:41 AM CST Category: Core

[bug #57546] [PATCH] make \[dd] transparent for end-of-sentence detection

Follow-up Comment #3, bug #57546 (project groff): [comment #2 comment #2:] > in Germany and Austria those two characters are *opening* delimiters. Ah, OK. Is that why the "[sic]" appears after the words "left guillemet" and "right guillemet" in man/groff_char.7.man? I had thought it had to do w

[bug #57556] Feature request: enforce left and right minimums as required by hyphenation patterns

URL: Summary: Feature request: enforce left and right minimums as required by hyphenation patterns Project: GNU troff Submitted by: barx Submitted on: Wed 08 Jan 2020 02:13:48 AM CST

[bug #57561] update US English hyphenation patterns

URL: Summary: update US English hyphenation patterns Project: GNU troff Submitted by: barx Submitted on: Wed 08 Jan 2020 06:31:57 PM CST Category: Macro - others Sever

  1   2   3   4   5   6   7   8   9   10   >