ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tomas Hala <tomas.hala@mendelu.cz>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupinteraction v commas
Date: Sat, 28 Mar 2020 11:27:40 +0100	[thread overview]
Message-ID: <20200328102732.GA23860@akela.mendelu.cz> (raw)
In-Reply-To: <6f9e7bb2-e8f7-0e84-3498-cdd10411c230@gmx.es>

Hi Pablo,

the data for attribute keywords is preprocessed also for other reasons, 
so there is no problem for me to add one gsub more.

Thank you very much for this sample.

Best wishes,

Tomáš

Fri, Mar 27, 2020 ve 06:06:21PM +0100 Pablo Rodriguez napsal(a):
# On 3/26/20 6:54 PM, Tomas Hala wrote:
# > [...]
# > I would like to have commas in metadata attribute keywords
# > because space is confusing -- one cannot distinguish
# > a space as a separator from a space as a part of a keyword.
# 
# Hi Tomáš,
# 
# a workaround is contained in the following sample
# 
#     \def\comma{‚}
#     \enabledirectives
#         [interaction.identity.preroll]
# 
#     \setupinteraction
#       [title={a, b, c},
#        subtitle={a, b, c},
#        author={a, b, c},
#        keyword={a\comma\ b\comma\ c},
#     ]
# 
#     \starttext
#     \null
#     \stoptext
# 
# BTW, I’m faking the character with an opening single comma (such as the
# one used in German [and probably other languages 😅]).
# 
# I don’t know how to insert the actual comma there, since it gets
# replaced when using the command.
# 
# Just in case it might help,
# 
# Pablo
# --
# http://www.ousia.tk
# ___________________________________________________________________________________
# If your question is of interest to others as well, please add an entry to the Wiki!
# 
# maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
# webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
# archive  : https://bitbucket.org/phg/context-mirror/commits/
# wiki     : http://contextgarden.net
# ___________________________________________________________________________________

                                         Tomáš Hála
--------------------------------------------------------------------
Mendelova univerzita, Provozně ekonomická fakulta, ústav informatiky
Zemědělská 1, CZ-613 00 Brno,  tel. +420 545 13 22 28
--------------------------------------------------------------------
http://akela.mendelu.cz/~thala
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-03-28 10:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 15:40 Tomas Hala
2020-03-26 17:34 ` Wolfgang Schuster
2020-03-26 17:54   ` Tomas Hala
2020-03-27 17:06     ` Pablo Rodriguez
2020-03-28 10:27       ` Tomas Hala [this message]
2020-03-28 12:20       ` Hans Hagen
2020-03-28 14:00         ` Tomas Hala
2020-03-28 15:07           ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200328102732.GA23860@akela.mendelu.cz \
    --to=tomas.hala@mendelu.cz \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).