[bug #62471] [tbl] horizontal and vertical rules are drawn too long in nroff mode

[G. Branden Robinson]

Update of bug#62471 (group groff):

  Status:None => In Progress


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #59933] Curly brackets displayed correctly in ps, but not in pdf

[Dave]

Follow-up Comment #6, bug#59933 (group groff):

Oliver, have you been able to confirm Deri's hypothesis that the problem you
were experiencing here was with the PDF viewer?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65092] Some text, testing

[Bjarni Ingi Gislason]

  bug-groff ticket #65092
  This has not happened before, therefore I repeat by sending
this through the web interface
"https://savannah.gnu.org/bugs/?group=groff";.

  If I send this with e-mail to bug-groff@gnu.org, there was
(is?) also some misdirection, that I do not remember what was.

The subject is: [bug #65092] Some text, testing

[bug #62830] [PATCH] [grops] support CJK fonts encoded in UTF16

[Deri James]

Follow-up Comment #12, bug#62830 (group groff):

Just a note to point out that gropdf (in the deri-gropdf-ng git branch)
already handles CJK documents. The attached pdf is an example, you should see
CJK in the pdf bookmarks as well.

(file #55489)

___

Additional Item Attachment:

File name: tanaka.pdf Size:32 KB



AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-ec09902a0a059b4d4d29a6c422be312926e7bc1e.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #62830] [PATCH] [grops] support CJK fonts encoded in UTF16

[Dave]

Follow-up Comment #11, bug#62830 (group groff):

[comment #9 comment #9:]
> It would be helpful to me if Messrs. Tanaka and Corff could
> reach a consensus on a schema for naming CJK font families.  :)

To assist in that, I'm adding Oliver to this bug's cc.  Oliver, do you have
any response to comment #10 here?  (You can post a comment to the bug report
without having to create a savannah account.)


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #62830] [PATCH] [grops] support CJK fonts encoded in UTF16

[TANAKA Takuji]

Follow-up Comment #10, bug#62830 (group groff):

I updated my patch to adjust to the latest upstream source code.

> While Mincho and Gothic loosely compare to serif and sans serif styles
> I think the font family classification terminology should be
language-agnostic

Thank Oliver for kind comments.
I agree that "M (stand for Mincho)",  "G (stand for Goshikku or Gothic)" are
not langage-agnostic.
However CJK language users require language specific fonts for each language.
In fact, Adobe have provided free CJK fonts "Source Han" and prepared 4 kinds
of localized font files
Simplified Chinese, Traditional Chinese, Japanese and Korean to support
regional variations.

https://source.typekit.com/source-han-serif/

I think 8 kinds of definitions for CJK (4 resional variations and 2 styles) is
minimum as basic fonts.
Since we need 4 resional variants, I do not think language-specific naming is
unappropreate for standard name.

"Source Han" has localized font names and they are consistent of my proposal.

Source Han Sans Simplified Chinese: 思源黑体 sīyuán hēitǐ :
CSH ; H stand for hēitǐ
Source Han Serif Simplified Chinese   : 思源宋体 sīyuán sòngtǐ:
CSS ; S stand for sòngtǐ

Source Han Sans Traditional Chinese   : 思源黑體 sīyuán hēitǐ :
CTH ; H stand for hēitǐ
Source Han Serif Traditional Chinese  : 思源宋體 sīyuán sòngtǐ:
CTS ; S stand for sòngtǐ

Source Han Sans Japanese  : 源ノ角ゴシック
Gen-no-kaku-goshikku : JPG ; G stand for Goshikku
Source Han Serif Japanese : 源ノ明朝   Gen-no-mincho  
 : JPM ; M stand for Mincho

Source Han Sans Korean: 본고딕   Bon GoTik   : KRG ; G
stand for Gotik
Source Han Serif Korean   : 본명조   Bon MyeongJo: KRM ; M
stand fo Myeongjo


If you still do not agree the langage-specific name,
langage-agnostic names based on English could be possible
for example CSSS, CSSR, CTSS, CTSR, JPSS, JPSR, KRSS, KRSR as followings:

Source Han Sans Simplified Chinese:: CSSS  SS stand for Sans-serif
Source Han Serif Simplified Chinese   :: CSSR  SR stand for Serif

Source Han Sans Traditional Chinese   :: CTSS
Source Han Serif Traditional Chinese  :: CTSR

Source Han Sans Japanese  :: JPSS
Source Han Serif Japanese :: JPSR

Source Han Sans Korean:: KRSS
Source Han Serif Korean   :: KRSR

Actually, I still recommend the formaer langage-specific ones.
But I accept the latter langage-agnostic ones if you do not agree my opinion.

Best,

(file #55487)

___

Additional Item Attachment:

File name: cjk-ps-html_20231223.patch Size:86 KB
   



AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-ec09902a0a059b4d4d29a6c422be312926e7bc1e.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #62776] [troff] want "style" warning category for self-deceptive inputs

[G. Branden Robinson]

Follow-up Comment #18, bug#62776 (group groff):

Correction to comment #17.

The user wants `\e` or (if the escape character is *not* the default) `\[rs]`
instead.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/