[NTG-context] misplaced border with scaled link

[NTG-context] misplaced border with scaled link

[Pablo Rodriguez via ntg-context]

Hi Hans,

since previous latest rotated link borders were fixed (as comments in
the sample), but scaled links got their border misplaced:

  \setupinteraction[state=start, color=, contrastcolor=, style=,]
  \enabledirectives[references.border=red]
  \setuppapersize[A6]
  \starttext
  \pagereference[æb]
  %~ \rotate[90]{Huge thanks for \at[æb]}\vfill
  %~ \rotate[90]{\at[æb]}\vfill
  \scale[width=.5tw]{\at[æb]}
  \stoptext

Could you take a look at this?

Many thanks for your help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Pablo Rodriguez via ntg-context]

On 2/14/26 11:20, Pablo Rodriguez via ntg-context wrote:
> Hi Hans,
> 
> since previous latest rotated link borders were fixed (as comments in
> the sample), but scaled links got their border misplaced:

I have just discovered that even the minimal scaling results in wrong
positioning of the link area:

  \setupinteraction[state=start, color=, contrastcolor=, style=,]
  \enabledirectives[references.border=red]
  \setuppapersize[A6]
  \starttext
  \startTEXpage[pagestate=start,offset=2ex]
  \pagereference[æb]
  \scale[height=8pt]{\at[æb]}
    {\at[æb]}
  \stopTEXpage
  \stoptext

But this only happens in LMTX, LuaTeX places the link area fine.

Could anyone confirm the issue?

Many thanks for your help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Jean-Pierre Delange via ntg-context]

[-- Attachment #1.1: Type: text/plain, Size: 2721 bytes --]

Hi Pablo,

I think I understand the issue you are pointing out. In your MWE, the 
visual content produced by |\at[æb]| is correctly scaled, but the 
clickable area (and the border drawn with |references.border|) no longer 
matches the scaled text in LMTX. In other words, the visual 
transformation seems to be applied, but the geometry of the link 
annotation does not seem to follow in the same way. What makes this 
particularly noticeable is that it already happens with very small 
scaling factors, and only in LMTX: with LuaTeX the link area still 
appears to be placed correctly. This suggests that the problem is not 
with |\at| itself, but with how link annotations interact with 
transformations such as |\scale| in the LMTX backend — possibly the 
annotation rectangle is computed before the transformation is applied, 
or is not transformed along with the box.

For reference, I am testing this with a ConTeXt version from July 2025. 
I haven’t yet checked whether different PDF viewers (e.g. Firefox / 
PDF.js versus native viewers) affect how the link borders are displayed, 
so that may also play a role. This is just my current reading of the 
behavior; I’d be interested to know whether this matches what others 
observe, or if I’m missing something.

Best regards,
JP


Le 19/02/2026 à 19:36, Pablo Rodriguez via ntg-context a écrit :
> On 2/14/26 11:20, Pablo Rodriguez via ntg-context wrote:
>> Hi Hans,
>>
>> since previous latest rotated link borders were fixed (as comments in
>> the sample), but scaled links got their border misplaced:
> I have just discovered that even the minimal scaling results in wrong
> positioning of the link area:
>
>    \setupinteraction[state=start, color=, contrastcolor=, style=,]
>    \enabledirectives[references.border=red]
>    \setuppapersize[A6]
>    \starttext
>    \startTEXpage[pagestate=start,offset=2ex]
>    \pagereference[æb]
>    \scale[height=8pt]{\at[æb]}
>      {\at[æb]}
>    \stopTEXpage
>    \stoptext
>
> But this only happens in LMTX, LuaTeX places the link area fine.
>
> Could anyone confirm the issue?
>
> Many thanks for your help,
>
> Pablo
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist :ntg-context@ntg.nl /https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  :https://www.pragma-ade.nl /https://context.aanhet.net (mirror)
> archive  :https://github.com/contextgarden/context
> wiki     :https://wiki.contextgarden.net
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 4241 bytes --]

[-- Attachment #2: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Pablo Rodriguez via ntg-context]

On 2/19/26 19:52, Jean-Pierre Delange via ntg-context wrote:
> Hi Pablo,
> 
> I think I understand the issue you are pointing out. In your MWE, the
> visual content produced by |\at[æb]| is correctly scaled, but the
> clickable area (and the border drawn with |references.border|) no longer
> matches the scaled text in LMTX. In other words, the visual
> transformation seems to be applied, but the geometry of the link
> annotation does not seem to follow in the same way. What makes this
> particularly noticeable is that it already happens with very small
> scaling factors, and only in LMTX: with LuaTeX the link area still
> appears to be placed correctly. This suggests that the problem is not
> with |\at| itself, but with how link annotations interact with
> transformations such as |\scale| in the LMTX backend — possibly the
> annotation rectangle is computed before the transformation is applied,
> or is not transformed along with the box.
> 
> For reference, I am testing this with a ConTeXt version from July 2025.
> I haven’t yet checked whether different PDF viewers (e.g. Firefox /
> PDF.js versus native viewers) affect how the link borders are displayed,
> so that may also play a role. This is just my current reading of the
> behavior; I’d be interested to know whether this matches what others
> observe, or if I’m missing something.

Sorry, Jean-Pierre, but would it be to much to as as confirmation either
of these brief replies?

  1. Yes, I can reproduce the issue.

  2. No, I cannot reproduce your issue.

Excuse me, but I don’t need a (machine-generated?) explanation (or
something virtually indistinguishable from it) from the issue I’m just
providing a sample. I think I know what I see on screen.

From your reply, I guess that you may have reproduced the issue.

I’m testing this with both 2026.02.12 13:41 and 2026.02.19 11:49 (both
Linux64). In both cases, LMTX draws the wrong link area and LuaTeX draws
it right.

Results of misplaced link area are consistent with current (as packaged
[and updated as of today] for “Fedora 43”) “Evince”/“Okular”, “MuPDF-GL”
and “XpdfReader”.

I think I might have hit a bug, asked for confirmation, so I’m not
missing something and it could be fixed.

Many thanks for your help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Jean-Pierre Delange via ntg-context]

Hi Pablo,

Sorry for the confusion.

Yes, I can reproduce the issue.

Best//JP


Le 20/02/2026 à 09:10, Pablo Rodriguez via ntg-context a écrit :
> On 2/19/26 19:52, Jean-Pierre Delange via ntg-context wrote:
>> Hi Pablo,
>>
>> I think I understand the issue you are pointing out. In your MWE, the
>> visual content produced by |\at[æb]| is correctly scaled, but the
>> clickable area (and the border drawn with |references.border|) no longer
>> matches the scaled text in LMTX. In other words, the visual
>> transformation seems to be applied, but the geometry of the link
>> annotation does not seem to follow in the same way. What makes this
>> particularly noticeable is that it already happens with very small
>> scaling factors, and only in LMTX: with LuaTeX the link area still
>> appears to be placed correctly. This suggests that the problem is not
>> with |\at| itself, but with how link annotations interact with
>> transformations such as |\scale| in the LMTX backend — possibly the
>> annotation rectangle is computed before the transformation is applied,
>> or is not transformed along with the box.
>>
>> For reference, I am testing this with a ConTeXt version from July 2025.
>> I haven’t yet checked whether different PDF viewers (e.g. Firefox /
>> PDF.js versus native viewers) affect how the link borders are displayed,
>> so that may also play a role. This is just my current reading of the
>> behavior; I’d be interested to know whether this matches what others
>> observe, or if I’m missing something.
> Sorry, Jean-Pierre, but would it be to much to as as confirmation either
> of these brief replies?
>
>    1. Yes, I can reproduce the issue.
>
>    2. No, I cannot reproduce your issue.
>
> Excuse me, but I don’t need a (machine-generated?) explanation (or
> something virtually indistinguishable from it) from the issue I’m just
> providing a sample. I think I know what I see on screen.
>
>  From your reply, I guess that you may have reproduced the issue.
>
> I’m testing this with both 2026.02.12 13:41 and 2026.02.19 11:49 (both
> Linux64). In both cases, LMTX draws the wrong link area and LuaTeX draws
> it right.
>
> Results of misplaced link area are consistent with current (as packaged
> [and updated as of today] for “Fedora 43”) “Evince”/“Okular”, “MuPDF-GL”
> and “XpdfReader”.
>
> I think I might have hit a bug, asked for confirmation, so I’m not
> missing something and it could be fixed.
>
> Many thanks for your help,
>
> Pablo
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive  : https://github.com/contextgarden/context
> wiki     : https://wiki.contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Jean-Pierre Delange via ntg-context]

[-- Attachment #1.1: Type: text/plain, Size: 5478 bytes --]

Hi Pablo,

sorry for the earlier noise ! To avoid relying on viewer behaviour, I 
tried to objectify the issue by inspecting the PDF objects directly. The 
method is simply to compare the |/Subtype /Link| annotations written 
into the PDF by each engine, in particular their |/Rect| values.

Specifically, I proceeded as you yourself indicated: compiling the 
source file with lmtx and with luatex :

  *

    context --engine=luatex  --result=border-luatex border-pablo.tex

  *

    context --engine=luametatex --result=border-lmtx border-pablo.tex

Then, extract the |/Rect [x0 y0 x1 y1]| values of the |/Link| 
annotations from the resulting PDFs (e.g. via PyPDF2 or mutool) . To 
achieve this (and to make the comparison independent of any PDF viewer), 
I used a very small inspection script on the PDF files themselves. The 
idea is simply to parse the PDF structure and list the annotations of 
type |/Subtype /Link|, then read their |/Rect [x0 y0 x1 y1]|entries. A 
minimal Python script using a standard PDF library (e.g. PyPDF2) is 
sufficient for this: it opens the PDF, iterates over |/Annots|on a given 
page, and prints the |/Rect|values for each link. Comparing these 
numeric rectangles between the LuaTeX and LMTX outputs makes it possible 
to identify whether the clickable area is already misplaced at 
PDF-generation level, independently of how viewers render it. Here below 
the two different values which show some issue in PDF production by LMTX :

border-luatex.pdf
   Link #1: /Rect [14.593437, 6.648379, 20.46615, 21.112035]
   Link #2: /Rect [24.361358, 6.660722, 30.216172, 21.080296]

border-lmtx.pdf
   Link #1: /Rect [14.677078, 6.638355, 20.660645, 21.080296]
   Link #2: /Rect [24.639551, 6.660722, 30.613851, 21.080296]

Doing so shows that (again), for the same source, the |/Rect| values 
differ between LuaTeX and LMTX, which explains the consistently 
misplaced clickable areas observed across viewers. Thanks for pointing 
this out, and sorry again for the confusion earlier. I hope this 
explanation sheds some light on the problem you encountered (although it 
doesn't explain why LMTX produces this difference!). As Hans has 
mentioned before, LMTX is not “LuaTeX with options” but a different 
engine, with its own backend and internal pipeline. I’ll leave it to him 
to explain whether this behaviour is expected, or if it can be improved.

Best//JP


Le 20/02/2026 à 09:10, Pablo Rodriguez via ntg-context a écrit :
> On 2/19/26 19:52, Jean-Pierre Delange via ntg-context wrote:
>> Hi Pablo,
>>
>> I think I understand the issue you are pointing out. In your MWE, the
>> visual content produced by |\at[æb]| is correctly scaled, but the
>> clickable area (and the border drawn with |references.border|) no longer
>> matches the scaled text in LMTX. In other words, the visual
>> transformation seems to be applied, but the geometry of the link
>> annotation does not seem to follow in the same way. What makes this
>> particularly noticeable is that it already happens with very small
>> scaling factors, and only in LMTX: with LuaTeX the link area still
>> appears to be placed correctly. This suggests that the problem is not
>> with |\at| itself, but with how link annotations interact with
>> transformations such as |\scale| in the LMTX backend — possibly the
>> annotation rectangle is computed before the transformation is applied,
>> or is not transformed along with the box.
>>
>> For reference, I am testing this with a ConTeXt version from July 2025.
>> I haven’t yet checked whether different PDF viewers (e.g. Firefox /
>> PDF.js versus native viewers) affect how the link borders are displayed,
>> so that may also play a role. This is just my current reading of the
>> behavior; I’d be interested to know whether this matches what others
>> observe, or if I’m missing something.
> Sorry, Jean-Pierre, but would it be to much to as as confirmation either
> of these brief replies?
>
>    1. Yes, I can reproduce the issue.
>
>    2. No, I cannot reproduce your issue.
>
> Excuse me, but I don’t need a (machine-generated?) explanation (or
> something virtually indistinguishable from it) from the issue I’m just
> providing a sample. I think I know what I see on screen.
>
>  From your reply, I guess that you may have reproduced the issue.
>
> I’m testing this with both 2026.02.12 13:41 and 2026.02.19 11:49 (both
> Linux64). In both cases, LMTX draws the wrong link area and LuaTeX draws
> it right.
>
> Results of misplaced link area are consistent with current (as packaged
> [and updated as of today] for “Fedora 43”) “Evince”/“Okular”, “MuPDF-GL”
> and “XpdfReader”.
>
> I think I might have hit a bug, asked for confirmation, so I’m not
> missing something and it could be fixed.
>
> Many thanks for your help,
>
> Pablo
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist :ntg-context@ntg.nl /https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  :https://www.pragma-ade.nl /https://context.aanhet.net (mirror)
> archive  :https://github.com/contextgarden/context
> wiki     :https://wiki.contextgarden.net
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 7139 bytes --]

[-- Attachment #2: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Pablo Rodriguez via ntg-context]

On 2/20/26 10:44, Jean-Pierre Delange via ntg-context wrote:
> Hi Pablo,
> 
> sorry for the earlier noise!

Dear Jean-Pierre,

you’re doing it again: no verbose explanation is needed.

Sorry, but I‘m starting to think that your messages are generated by AI
(rather than entirely written by you). If that were the case, for the
second time, please refrain from doing it.

But since it seems that you ask for it, I will give you mine.

I’m used to read PDF code. In fact, I have a small _Unix_ script
(`uncompress-pdf`) with the following contents:

  mutool clean -d "$1" uncompressed-"$1" && nvim uncompressed-"$1"

I agree, it may be improved, but it fits my (otherwise, extremely basic)
needs.

Excuse me for having to say this, but that way I could help to fix
digital signatures in ConTeXt (also, that could be handled right by
“Acrobat Reader”) and signature fields (different issues), among few
other ones.

In this case, it was clear to me that `/Rect` was wrong written (by
LMTX, I’m afraid) and well read by the PDF viewers.

If I had the slightest suspicion that `/Rect` was written right and read
wrong, I’d have checked that in the PDF code and I’d have reported the
issue to the developers of the PDF viewers.

I know that LMTX isn’t LuaTeX and I think this is probably a bug.

As for the new composition style in your messages, I recognize I have an
issue here: I can’t stand AI-generated text (or a similar output).

In this sense, I’m far worse than “The Princess and the Pea”: I cannot
stand even a single layer of the pea‘s peel. Just in case this weren’t
clear, I think the difference is clear with AI-generated slop.

In contrast, I think that your previous messages were more interesting
(or so they seemed to me).

But the longer we speak, the less things I will be able to get done this
morning.

Best wishes,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Jean-Pierre Delange via ntg-context]

[-- Attachment #1.1: Type: text/plain, Size: 3076 bytes --]

Dear Pablo,

just to clarify my intention, briefly.

I wasn’t trying to explain anything /to you/. When you raised the issue, 
I took it as something that might also be of interest to other readers 
of the list (myself included), and I responded in that spirit — trying 
to understand what is going on and how one can reason about it.

That said, I understand your preference for very concise exchanges, and 
I’ll adapt accordingly.

Best//Jean-Pierre


Le 20/02/2026 à 11:24, Pablo Rodriguez via ntg-context a écrit :
> On 2/20/26 10:44, Jean-Pierre Delange via ntg-context wrote:
>> Hi Pablo,
>>
>> sorry for the earlier noise!
> Dear Jean-Pierre,
>
> you’re doing it again: no verbose explanation is needed.
>
> Sorry, but I‘m starting to think that your messages are generated by AI
> (rather than entirely written by you). If that were the case, for the
> second time, please refrain from doing it.
>
> But since it seems that you ask for it, I will give you mine.
>
> I’m used to read PDF code. In fact, I have a small _Unix_ script
> (`uncompress-pdf`) with the following contents:
>
>    mutool clean -d "$1" uncompressed-"$1" && nvim uncompressed-"$1"
>
> I agree, it may be improved, but it fits my (otherwise, extremely basic)
> needs.
>
> Excuse me for having to say this, but that way I could help to fix
> digital signatures in ConTeXt (also, that could be handled right by
> “Acrobat Reader”) and signature fields (different issues), among few
> other ones.
>
> In this case, it was clear to me that `/Rect` was wrong written (by
> LMTX, I’m afraid) and well read by the PDF viewers.
>
> If I had the slightest suspicion that `/Rect` was written right and read
> wrong, I’d have checked that in the PDF code and I’d have reported the
> issue to the developers of the PDF viewers.
>
> I know that LMTX isn’t LuaTeX and I think this is probably a bug.
>
> As for the new composition style in your messages, I recognize I have an
> issue here: I can’t stand AI-generated text (or a similar output).
>
> In this sense, I’m far worse than “The Princess and the Pea”: I cannot
> stand even a single layer of the pea‘s peel. Just in case this weren’t
> clear, I think the difference is clear with AI-generated slop.
>
> In contrast, I think that your previous messages were more interesting
> (or so they seemed to me).
>
> But the longer we speak, the less things I will be able to get done this
> morning.
>
> Best wishes,
>
> Pablo
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist :ntg-context@ntg.nl /https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  :https://www.pragma-ade.nl /https://context.aanhet.net (mirror)
> archive  :https://github.com/contextgarden/context
> wiki     :https://wiki.contextgarden.net
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 4081 bytes --]

[-- Attachment #2: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Pablo Rodriguez via ntg-context]

On 2/20/26 11:24, Pablo Rodriguez via ntg-context wrote:
> […]
> I know that LMTX isn’t LuaTeX and I think this is probably a bug.

Sorry, my fault here. The bug comes from the sample, not of course for
LMTX not being LuaTeX.

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

[NTG-context] Re: misplaced border with scaled link

[Pablo Rodriguez via ntg-context]

On 2/20/26 12:34, Jean-Pierre Delange via ntg-context wrote:
> Dear Pablo,
> 
> just to clarify my intention, briefly.
> 
> I wasn’t trying to explain anything /to you/.

My apologies, Jean-Pierre.

I’m not offended, but I considered the explanation as obvious (and not
very digestible when the details come in) for many users.

Sorry, I may have taken for granted that if a rectangle is drawn where
it shouldn’t, it is because its coordinates are miscalculated.

My impression is also that (probably to due to consumption of
AI-generated texts) many people prefer lengthy (and not always clear)
texts over clear and concise messages.

It isn‘t especially about this thread, but humans don’t live much more
than a century (most live clearly less): no point in reading
unnecessarily large texts.

Many thanks for your readiness to help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________