Re: Inconsistent Japanese name order in v13 contributors list - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Inconsistent Japanese name order in v13 contributors list
Date
Msg-id 20200924203155.GE22807@momjian.us
Whole thread Raw
In response to Re: Inconsistent Japanese name order in v13 contributors list  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Mon, Sep 21, 2020 at 10:31:31AM -0300, Alvaro Herrera wrote:
> On 2020-Sep-18, Bruce Momjian wrote:
> 
> > This thread from 2015 is the most comprehensive discussion I remember of
> > Japanese name ordering, including a suggestion to use small caps:
> > 
> >
https://www.postgresql.org/message-id/flat/20150613231826.GY133018%40postgresql.org#88d245a5cdd2b32e1e3e80fc07eab6f2
> > 
> > I have been following this guidance ever since.
> 
> Right.
> 
> About smallcaps, we didn't do it then because there was no way known to
> us to use them in our then-current toolchain.  But we've changed now to
> XML and apparently it is possible to use them -- we could try something
> like <emphasis role="caps_lastname"> and define a CSS rule like
> 
> .caps_lastname {font-variant: small-caps;}

Yes, that's what I use for CSS.

> (Apparently you also need to set 'emphasis.propagates.style' to 1 in the
> stylesheet).  This does it for HTML.  You also need some FO trick to
> cover the PDF (probably something like what a042750646db did to change
> catalog_table_entry formatting.)

Yeah, we have PDF output to worry about too.  It is easy in LaTeX.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: Custom options for building extensions with --with--llvm
Next
From: Anastasia Lubennikova
Date:
Subject: Re: [PATCH] Automatic HASH and LIST partition creation