LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Thu, 27 Dec 2018 08:55:44 +0000
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=utf-8; format=flowed
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (41 lines)
On 27/12/2018 08:26, Tisha Shusho wrote:
> Hello List,
> Merry Christmas and a Happy New Year in advance.
> I want to apply the function '\exp_args:Ncnn' to
> '\fontspec_set_family:Nnn <family-passed-as-list-of-strings> <feature> 
> <font>'.
> Please note the family name is defined as a variable l__..._tl. The 
> reason that
> I want to 'Ncnn' (I think) is that the argument specification of the 
> function
> '\fontspec_set_family' is 'Nnn'.
> However, there is no argument specification 'Ncnn' in the signature of
> '\exp_args'. Also as I understand from the LaTeX3 documents it is not
> possible to create such a variant for this function with
> '\cs_generate_variant:Nn'. Furthermore, as '\exp_args_generate:n' is
> defined in 'l3candidates' which is experimental, at the moment I have
> decided to use the following:
> \exp_args:Ncnx \fontspec_set_family:Nnn 
> <family-passed-as-list-of-strings> <feature> <font>'
> Is it correct to use 'Ncnx' instead of 'Ncnn'? What is the best
> argument specification to use instead of 'Ncnx' here?
> Thanks,
> Tisha

You should be making a variant, but you can't have a c-type variant for 
an n-type parent. Instead, you want to pass the value of a csname: 
that's v-type

   \cs_generate_variant:Nn \fontspec_set_family:Nnn { Nv }
   \fontspec_set_family:Nvn \fontspec_set_family:Nnn \sometoken
     { l_tmpa_tl } % or whatever
     { ... }