<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Apparently we are talking past each other.<div><br></div><div>I understand the argument. The elision mark is not an accent. It is a letter character when used between letters but a punctuation character (so a word break character) when at the beginning or end of words. It has been requested of the Unicode consortium to make it a letter character when it follows a Greek letter, but this has not been done. The goal of the request is that double clicking on the Greek word ending with U+2019 would also select the apostrophe in the same way that it does when it is in the middle of a character sequence.</div><div><br></div><div>I’m saying if the filter does double duty for both presentation and normalization of search requests, then both have to work well.</div><div><br></div><div>That U+2019 is visually similar to U+0027 and an end user will use the keyboard to type U+0027 when U+2019 is required. This will not work as the exact code point has to match.</div><div><br></div><div>Over the years, I’ve found that simple code changes often break other parts of the code.</div><div><br></div><div>I’ve requested to examine the search code in Xiphos to see if another filter is applied that strips U+2019. If so, then your request probably will work. However, if Xiphos needs to be changed in addition to SWORD lib to accommodate the change, then probably every frontend would need to be changed.</div><div><br></div><div>Also, I need to dig into the Lucene index creation and Lucene search to make sure it doesn’t require indexes to be rebuilt.</div><div><br></div><div>DM<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Mar 18, 2025, at 3:21 AM, David Haslam <dfhdfh@protonmail.com> wrote:</div><br class="Apple-interchange-newline"><div><div style="font-family: Arial, sans-serif; font-size: 14px;">We don't hide U+2019 in any other context.</div><div style="font-family: Arial, sans-serif; font-size: 14px;">It's use in the KJV for possessives does not hinder search!</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;">Why the obsession with search, when it has no bearing on my semantic argument?</div><div style="font-family: Arial, sans-serif; font-size: 14px;">An elision mark is simply not an accent!!! Why is this so hard to understand?</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;">We wouldn't hide U+2019 in French if we saw it used frequently as an elision mark!!!</div><div style="font-family: Arial, sans-serif; font-size: 14px;">Albeit most French modules to date simply use U+0027 (unlike our KJV).</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div>
<div class="protonmail_signature_block" style="font-family: Arial, sans-serif; font-size: 14px;">
<div class="protonmail_signature_block-user">
Best regards,<br><br>David
</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div>
<div class="protonmail_signature_block-proton">
Sent with <a target="_blank" href="https://pr.tn/ref/SWXT9A5YZ67G">Proton Mail</a> secure email.
</div>
</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div class="protonmail_quote">
On Tuesday, March 18th, 2025 at 1:40 AM, DM Smith <dmsmith@crosswire.org> wrote:<br>
<blockquote class="protonmail_quote" type="cite">
<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Mar 17, 2025, at 5:24 PM, David Haslam <dfhdfh@protonmail.com> wrote:</div><br class="Apple-interchange-newline"><div><div> <div dir="auto">My argument is simple & straightforward.</div></div></div></blockquote><div><br></div>Your argument is that display and search should have nothing to do with each other.</div><div><br><blockquote type="cite"><div><div><div dir="auto"><br></div><div dir="auto">When you hide diacritics, you ought not to be hiding punctuation marks.</div><div dir="auto"><br></div><div dir="auto">Why is this so contentious?</div></div></div></blockquote><div><br></div>Software changes can have unintended consequences. It needs to be carefully considered.</div><div><br><blockquote type="cite"><div><div><div dir="auto"><br></div><div dir="auto">In what world does how a module displays require that punctuation be hidden?</div></div></div></blockquote><div><br></div>In a world where the filter is also used for search.<br><blockquote type="cite"><div><div><div dir="auto"><br></div><div dir="auto">A quotation mark is not an accent! </div><div dir="auto"><br></div><div dir="auto">David</div><div><br></div> <div><br></div><div><br></div>On Mon, Mar 17, 2025 at 21:06, DM Smith <<a href="mailto:On Mon, Mar 17, 2025 at 21:06, DM Smith <<a href=" rel="noreferrer nofollow noopener">dmsmith@crosswire.org</a>> wrote:<blockquote class="protonmail_quote" type="cite"> <br id="lineBreakAtBeginningOfMessage">
<div>
<br>
<blockquote type="cite">
<div>
On Mar 17, 2025, at 4:01 PM, Karl Kleinpaste <karl@kleinpaste.org> wrote:
</div>
<br class="Apple-interchange-newline">
<div>
<span style="caret-color: rgb(0, 0, 0); font-family: FreeSerif; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">That is, if search success depends on the specificity of whether accents or points are enabled, you're probably doing something wrong.</span>
<br style="caret-color: rgb(0, 0, 0); font-family: FreeSerif; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
</div>
</blockquote>
<br>
</div>
<div>
Absolutely.
</div>
<div>
<br>
</div>
<div>
What we are discussing is whether an apostrophe should be stripped out or not. The apostrophe on the keyboard is U+0027. The apostrophe in the Greek is recommended to be U+2019. They look nearly the same. There are a few other Unicode apostrophes that have the same appearance.
</div>
<div>
<br>
</div>
<div>
If the apostrophe isn’t stripped out, then the user input and the text have to agree on which of the several it is. There is no way for the end user to know which. I end up copying from the text to make sure I have the right one.
</div>
<div>
<br>
</div>
<div>
I believe the same filter that turns on and off the display of accents is used for searching. David is suggesting that the filter is taking out legitimate level 2 quotation marks from the display when it shouldn’t. I’m suggesting that it needs to remove them for the sake of the search.
</div>
<div>
<br>
</div>
<div>
DM
</div></blockquote></div>_______________________________________________<br>sword-devel mailing list: sword-devel@crosswire.org<br>http://crosswire.org/mailman/listinfo/sword-devel<br>Instructions to unsubscribe/change your settings at above page<br></div></blockquote></div><br>
</blockquote><br>
</div>_______________________________________________<br>sword-devel mailing list: sword-devel@crosswire.org<br>http://crosswire.org/mailman/listinfo/sword-devel<br>Instructions to unsubscribe/change your settings at above page<br></div></blockquote></div><br></div></body></html>