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>
            <DA3F46D9-8BD3-47B0-8BFC-260C74FD7F65@gmx.at>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
            Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID:  <23eee84b-ea67-be90-6ac4-483f38a54452@latex-project.org>
Date:         Sun, 23 Apr 2017 11:37:19 +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:         Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: Using d<> and babel with option spanish
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <DA3F46D9-8BD3-47B0-8BFC-260C74FD7F65@gmx.at>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

Am 23.04.17 um 10:50 schrieb Benedikt Vitecek:
> 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.


as I expected, babel does have an option to enable the shorthands 
already in the preamble:

[KeepShorthandsActive]

however, as I also expected that doesn't  work in all cases as  packages 
loaded afterwards may have a problem with that.


So

   \usepackage{xparse}

   \usepackage
     [KeepShorthandsActive]
     {babel}

solves your problem but if babel is loaded before xparse, that will break.

On the other hand, what might be enough in your case is simply changing 
the catcode of < and > before making your definition since we know that 
it will be active by the time of begin document (ie when your definition 
is used):


   \documentclass[spanish]{scrartcl}

   \usepackage{xparse}

   \usepackage{babel}

\catcode`\< = 13
\catcode`\> = 13

   \NewDocumentCommand \Something { d<> m }
     {
       Optional: #1 \\
       Mandatory: #2
     }
  \catcode`\< = 12
  \catcode`\> = 12


   \begin{document}
   \Something<Hello>{World}
   \end{document}

Of course that only works because we know that spanish will activate 
them, so this is not robust in a general way.

Guess the correct answer is drawingboard and make xparse babel aware and 
long term a better shorthand interface / integration

frank