\setupinteraction v commas

\setupinteraction v commas

[Tomas Hala]

Hi all, 

I used the following MWE for creating the metainformation in PDF:

\setupinteraction
  [title={a, b, c},
   subtitle={a, b, c},
   author={a, b, c},
   keyword={a, b, c},
]

\starttext 
blah
\stoptext

While the title, subtitle and author contain the text without any change, 
in keyword all commas has been erased. Is this the expected behaviour?
If yes, how could I write command inside?

Best wishes,

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
___________________________________________________________________________________

Re: \setupinteraction v commas

[Wolfgang Schuster]

Tomas Hala schrieb am 26.03.2020 um 16:40:
> Hi all,
> 
> I used the following MWE for creating the metainformation in PDF:
> 
> \setupinteraction
>    [title={a, b, c},
>     subtitle={a, b, c},
>     author={a, b, c},
>     keyword={a, b, c},
> ]
> 
> \starttext
> blah
> \stoptext
> 
> While the title, subtitle and author contain the text without any change,
> in keyword all commas has been erased. Is this the expected behaviour?

Yes, the comma is used as separator for keywords and replaced with a 
space in the metadata.

> If yes, how could I write command inside?

???

Wolfgang

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: \setupinteraction v commas

[Tomas Hala]

Thu, Mar 26, 2020 ve 06:34:28PM +0100 Wolfgang Schuster napsal(a):
# Tomas Hala schrieb am 26.03.2020 um 16:40:
# >Hi all,
# >
# >I used the following MWE for creating the metainformation in PDF:
# >
# >\setupinteraction
# >   [title={a, b, c},
# >    subtitle={a, b, c},
# >    author={a, b, c},
# >    keyword={a, b, c},
# >]
# >
# >\starttext
# >blah
# >\stoptext
# >
# >While the title, subtitle and author contain the text without any change,
# >in keyword all commas has been erased. Is this the expected behaviour?
# 
# Yes, the comma is used as separator for keywords and replaced with a
# space in the metadata.
# 
# >If yes, how could I write command inside?
# 
# ???
#
# Wolfgang

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.

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
___________________________________________________________________________________

Re: \setupinteraction v commas

[Pablo Rodriguez]

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
___________________________________________________________________________________

Re: \setupinteraction v commas

[Tomas Hala]

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
___________________________________________________________________________________

Re: \setupinteraction v commas

[Hans Hagen]

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

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: \setupinteraction v commas

[Tomas Hala]

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
___________________________________________________________________________________

Re: \setupinteraction v commas

[Hans Hagen]

On 3/28/2020 3:00 PM, Tomas Hala wrote:
> 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.

Normally when something is applied (like here removing commas) there is 
a reason (here we're talking of very old features so i would not be 
surprised id some older acrobat liked it more when displaying them and 
often these older feature are made such that acrobat was served). And 
pdf data structures are not something typeset, which for means means: 
'word' is just that 'word'.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________