Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
References: <CALD=Yf_Qn4av1BbUzVgg_LtRS7JW_cOngjHHCyxbOn7g-2rs4g@mail.gmail.com> <87h91h7lsa.fsf@fencepost.gnu.org>
            <CALD=Yf9mQHd-BdWmqGDap5Y9SuR63sii6QvVF5=zjC-+nb7PVg@mail.gmail.com>
            <b2a6f653-5366-8d2c-cbbc-e13458f9d51c@latex-project.org>
            <710D47B3-391D-42C2-8D5B-B58AB23F29B1@gmx.at>
            <76ba7fdb-921c-ec17-e34c-bd5562b3960e@gmail.com>
Message-ID:  <DA3F46D9-8BD3-47B0-8BFC-260C74FD7F65@gmx.at>
Date:         Sun, 23 Apr 2017 10:50:39 +0200
Reply-To:     Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender:       Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From:         Benedikt Vitecek <b.vitecek@GMX.AT>
Subject: Re: Using d<> and babel with option spanish
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <76ba7fdb-921c-ec17-e34c-bd5562b3960e@gmail.com>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Content-Transfer-Encoding: 8bit
Status: R

> What happens if you do your definition \AtBeginDocument?  Does babel
> turn on shorthands too late for that?

I’ve tried it before and sadly it doesn’t work and produces the same output:

  \documentclass[spanish]{scrartcl}
  \usepackage{babel}
  \usepackage{xparse}
  \ExplSyntaxOn
  \AtBeginDocument{
  \NewDocumentCommand \Something { d<> m }
    {
      Optional: #1 \\
      Mandatory: #2 \\
      Other: 
    }
  }
  \ExplSyntaxOff
  \begin{document}
  \Something<Hello>{World}
  \end{document}

> Here at some point the
> command you define must grab an argument delimited by ">".  Given how
> TeX works, we need to know what category code this ">" will have.  In
> principle it could be conceivable to do that depending on the category
> code of the "<" that started the argument, or depending on the current
> category code of ">"


I am glad that this is the first (maybe second) time I have to deal with category codes, 
it seems to be quite complicated.

I think what I might be able to do locally is to check if the „m“ argument grabs the token
„<„ (which I should be able to test with \str_if_eq:nn {#2} { < } ), define a macro which collects the 
next tokens until it encounters a „>“ (again tested with \str_if_eq:nn) and then maybe call my
main command again.

This is only a rough idea and I would need to figure out how to implement it, but it could solve (at least
for me) the category code problem. 

Ben