- Fixed global flag on regex subs
- Change the Decode module to the old module name (in case it is linked
by someone)
- Fix attribution links, add ‘crazedpsyc’ to attribution section in the
new module
- Add a comment about the separation of the encode and decode
functionality
- Fix test file for the module name change
This is an attempt to add the requested "squared" operation without all
of the nasty trigger changes I introduced last time I tried.
Also added a constant for 'score' as both an attempt to better
understand that trigger regex and an historical oddity.
It's clear that if I want to continue with this I should make a lexer.
– Add HTMLEntitiesDecode.pm and .t
– Add HTMLEntitiesEncode.pm and .t
– Add URLEncode and .t
– Remove HTMLEntities.pm and HTMLEntitiesCode.pm and their test files
– Initial commit perl module
– Initial commit test file
– Displays the “maybe inaccurate” message for android devices by using
JavaScript to get the user-agent
– Contains commented out lines of JavaScript code that can be enabled
to not show any resolution numbers if device user-agent is Android
- regex to clean up whitespaces and to remove filler words (for, of)
- symbol and sign presence/absence in query does not make a difference
in hits
- all ‘-‘ are replaced by ’ ‘.
- accented_chars keys have no spaces now
- updated triggers
HTMLEntitiesCodes.pm
1. Substring replacers
A few practical examples as a result of this change — the following
query pairs will now lookup the same key: ‘trademark symbol’ and
‘trademark’ // ‘up-down arrow’ and ‘up down arrow’ // ‘pound sign’ and
‘pound’, and so on…
2. Update the keys for this change (extraneous keys removed).
This mostly just adds style to the HTML answers to be more in line with
other IAs.
The test changes are because, in general, the HTML answer is exactly the
same as the text answer, just wrapped up in some HTML. We're mostly
concerned with if we get correct answers, not how they happen to be
wrapped for HTML display.
In cases where that's different (the <sup> regression) we do more
thorough testing on the contents.
Also, removed one repeated test.
I'm starting to think this "apply_css" and maybe even "wrap_html" should
be in a role somewhere.
Total run time may well exceed 1 second with the pre- and post-
processing, but this makes it significantly less annoying to try things
out with `duckpan query`.
Also adds a test which shows the `duckpan query` parameters I was
trying, showing how `squared` is applied (and may result in confusion)