[OS X TeX] Customize brackets/braces/parens/delimiters TexShop matching

Herbert Schulz herbs at wideopenwest.com
Mon Feb 12 12:38:56 EST 2018


> On Feb 12, 2018, at 11:03 AM, Claus Gerhardt <claus.gerhardt at uni-heidelberg.de> wrote:
> 
> I am recommending a macro, e.g., my macro for the German quotes, which I occasionally use, is 
> 
> \newcommand{\cq}[1]{\glqq{#1}\grqq\,}
> 
> Claus
> 
>> On 12. Feb 2018, at 14:09, Juan Acevedo <juan.acevedo at gmx.net> wrote:
>> 
>> Thanks Dick for the jet-lagged answer. I was hoping you would step in, and no need to apologise.
>> 
>> I do understand the complications of intending to match " and < as delimiters, but this is not what I mean, as has been noticed now, because it is all in a UTF8 context.
>> 
>> What I mean is something already provided by default in TeXworks. I appreciate TeXworks, but TeXShop... frankly, I can hardly spend a day without using it (with constant gratitude too), and since this feature would not seem to be a hard thing to add...
>> 
>> The characters that would need to be recognised as delimiters are:
>> 
>> U+201C 	LEFT DOUBLE QUOTATION MARK
>> U+201D 	RIGHT DOUBLE QUOTATION MARK
>> 
>> U+00AB LEFT-POINTING DOUBLE ANGLE QUOTATION MARK (these are the guillemets)
>> U+00BB RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK
>> 
>> But in fact, to keep things simple, instead of adding a feature for everyone, would it be possible to just allow users to activate their language-specific delimiters, I mean like CJK corner brackets (U+300C and U+300D), or „German“ double quotes... Maybe a hidden preference, or a document in Library that can be edited?
>> 
>> Why all this?
>> I'm no programmer. Sometimes, when importing OCR'd text or simply badly formatted documents into TeX, delimiter matching is of great help to prepare the pages for csquotes parsing through them. In my case this is a tool for "debugging" long documents in preparation for TeX typesetting.
>> 
>> Cheers,
>> J

Howdy,

But the Source looks so much better when you type the characters directly and use UTF-8 (or some other extension encoding).

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)





More information about the MacOSX-TeX mailing list