From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Bug in verbatim wrapping examples on wiki
Date: Sun, 5 Feb 2023 12:32:42 +0100 [thread overview]
Message-ID: <6f0b0ad5-e70f-a17f-bf26-9f6fdd18affb@gmx.es> (raw)
In-Reply-To: <dda6b456-9340-3f9a-752e-670539827ce9@gmx.es>
On 2/4/23 10:37, Pablo Rodriguez via ntg-context wrote:
> On 2/4/23 07:49, Hugo Landau via ntg-context wrote:
>> On this page of the wiki there is an example for wrapping long words,
>> like long hexadecimal strings:
>>
>> https://wiki.contextgarden.net/Wrapping
>>
>> This example is buggy because it deletes one character at the point that
>> it is wrapped.
>>
>> Anyone have a solution?
>
> Many thanks for your report, Hugo.
>
> I use this code from time to time and I totally overlooked this.
>
> Have you checked all options that the sample contains?
Hans,
I have just checked that these line breakings loose a character in all
options.
The next sample displays the issue clearly:
\startluacode
--local shared = {
-- start = 1,
-- length = 1,
-- left = false,
-- right = false,
--}
local shared = {
start = 1,
length = 1,
before = utf.char(0xB7),
after = nil,
left = false,
right = false,
}
-- languages.hyphenators.traditional.installmethod("sha",
-- function(dictionary,word,n)
-- local t = { }
-- for i=1,#word do
-- t[i] = shared
-- end
-- return t
-- end
-- )
-- or more efficient when used often:
-- local all = { }
-- for i=1,512 do
-- all[i] = shared
-- end
-- languages.hyphenators.traditional.installmethod("sha",
-- function(dictionary,word,n)
-- return all
-- end
-- )
-- or more obscure:
-- local all = table.setmetatableindex({ }, function(t,k)
-- t[k] = shared
-- return shared
-- end)
--
-- languages.hyphenators.traditional.installmethod("sha",
-- function(dictionary,word,n)
-- return all
-- end
-- )
-- or just (lua is fast enough anyway)
local all = table.setmetatableindex({ }, function(t,k)
return shared
end)
languages.hyphenators.traditional.installmethod("sha",
function(dictionary,word,n)
return all
end
)
\stopluacode
\definehyphenationfeatures
[sha]
[characters=all,
alternative=sha]
\unexpanded\def\sha#1%
{\begingroup
\sethyphenationfeatures[sha]%
#1%
\endgroup}
\setuphyphenation[method=traditional]
%
% \unexpanded\def\sha#1%
% {\begingroup
% \sethyphenationfeatures[sha]%
% \setuphyphenation[method=traditional]%
% #1%
% \endgroup}
\starttext
\hyphenatedword{\sha{8b2f3c087046c3943ace0dc4f958ef2138e58a51b40e%
ef6fab6fa1aeb845cc257a410ab1b914bc399b4293f%
31c76fc2c73e5be5ea4d329f9e6820984688efec2}}
\stoptext
Are we missing something or is this a bug?
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://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-02-05 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 6:49 Hugo Landau via ntg-context
2023-02-04 9:37 ` Pablo Rodriguez via ntg-context
2023-02-05 11:32 ` Pablo Rodriguez via ntg-context [this message]
2023-02-05 11:50 ` Floris van Manen via ntg-context
2023-02-05 12:13 ` Hans Hagen via ntg-context
2023-02-05 15:52 ` Pablo Rodriguez via ntg-context
2023-02-06 17:59 ` Hans Hagen via ntg-context
2023-02-15 18:35 ` Pablo Rodriguez via ntg-context
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=6f0b0ad5-e70f-a17f-bf26-9f6fdd18affb@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).