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 15:00:10 +0100 [thread overview]
Message-ID: <20200328140010.GB23860@akela.mendelu.cz> (raw)
In-Reply-To: <714b9591-6923-cfc6-8ef4-cc13257abcef@xs4all.nl>
Sat, Mar 28, 2020 ve 01:20:26PM +0100 Hans Hagen napsal(a):
# On 3/27/2020 6:06 PM, Pablo Rodriguez wrote:
# >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,
# It's no big deal to support
#
# keyword={{a, b, c}},
#
# which then gives:
#
# <pdf:Keywords>a, b, c</pdf:Keywords>
#
# but then you end up with
#
# keyword={{a, b, c},{d, e, d}},
#
# becoming
#
# <pdf:Keywords>a, b, c d, e, f</pdf:Keywords>
#
# i wonder what, after encountering this, the next request will be ...
#
# anyway, I suppose you will check what different viewers make of that
# when they display/handle keywords and wikify it
#
# Hans
I am afraid that there is nothing to be wikified... I opened it
(Mint 19.3/64b) in qpdfview and evince, print out by pdfinfo and mutool
and in all cases there is "a b c" or "a, b, c" (, = single left quote)
as was written. (My acroread is just broken and in xpdf and mupdf
I guess there is no service to display it.)
What is the reason that keyword attribute does not accept commas whereas
others (title, author...) do?
# keyword={{a, b, c}},
As far as I know, key words (in papers, books etc.) are used only as a comma
separated list of terms without further structuring so I cannot imagine
who and why would need braces in normal cases.
Tomáš
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-03-28 14:00 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
2020-03-28 12:20 ` Hans Hagen
2020-03-28 14:00 ` Tomas Hala [this message]
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=20200328140010.GB23860@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).