<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[TextFX Proper Case does not handle 's properly]]></title><description><![CDATA[<p dir="auto">if you convert google’s you get Google’S while it should be Google’s.</p>
<p dir="auto">Not sure if this is the right place to report this or if this is the intended behavior. Thanks!</p>
]]></description><link>https://community.notepad-plus-plus.org/topic/10584/textfx-proper-case-does-not-handle-s-properly</link><generator>RSS for Node</generator><lastBuildDate>Tue, 06 Oct 2026 16:51:59 GMT</lastBuildDate><atom:link href="https://community.notepad-plus-plus.org/topic/10584.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 27 Sep 2015 01:46:12 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to TextFX Proper Case does not handle 's properly on Tue, 27 Sep 2022 21:43:59 GMT]]></title><description><![CDATA[<p dir="auto">Hi, <strong>all</strong>,</p>
<p dir="auto">With the <strong>last</strong> version <strong><code>v8.4.6</code></strong>, I’ve just tried to use the <strong><code>Edit &gt; Convert Case to &gt; Proper Case</code></strong> option against this <em>INPUT</em> text :</p>
<pre><code class="language-diff">McDonald
MacDonald
O'Neil
Google's
A FBI Inspector
my.email@test.com
John Smith III
</code></pre>
<p dir="auto">And I get :</p>
<pre><code class="language-diff">Mcdonald
Macdonald
O'neil
Google's
A Fbi Inspector
My.Email@Test.Com
John Smith Iii
</code></pre>
<hr />
<p dir="auto">Now, if I use the <strong><code>Edit &gt; Convert Case to &gt; Proper Case (blend)</code></strong> option against this <strong>same</strong> <em>INPUT</em> text, I get :</p>
<pre><code class="language-diff">McDonald
MacDonald
O'neil
Google's
A FBI Inspector
My.Email@Test.Com
John Smith III
</code></pre>
<hr />
<p dir="auto">Note that, <strong>whatever</strong> your choice, most of these expressions are <strong>not</strong> correct, <strong>after</strong> modifications !</p>
<p dir="auto">Refer, my <strong>previous</strong> post of <strong><code>2015</code></strong>, above !</p>
<p dir="auto">Best Regards,</p>
<p dir="auto">guy038</p>
<p dir="auto">Funny : Exactly <strong>seven</strong> years, to the day, between my <strong>two</strong> posts !!</p>
]]></description><link>https://community.notepad-plus-plus.org/post/80137</link><guid isPermaLink="true">https://community.notepad-plus-plus.org/post/80137</guid><dc:creator><![CDATA[guy038]]></dc:creator><pubDate>Tue, 27 Sep 2022 21:43:59 GMT</pubDate></item><item><title><![CDATA[Reply to TextFX Proper Case does not handle 's properly on Sun, 27 Sep 2015 17:56:19 GMT]]></title><description><![CDATA[<p dir="auto">You are right. It would need something smarter to power the backend engine like Google’s spell checker. I would check out your connected post as well. Thanks!</p>
]]></description><link>https://community.notepad-plus-plus.org/post/11525</link><guid isPermaLink="true">https://community.notepad-plus-plus.org/post/11525</guid><dc:creator><![CDATA[Sushubh Mittal]]></dc:creator><pubDate>Sun, 27 Sep 2015 17:56:19 GMT</pubDate></item><item><title><![CDATA[Reply to TextFX Proper Case does not handle 's properly on Sun, 27 Sep 2015 09:37:36 GMT]]></title><description><![CDATA[<p dir="auto">Hello <strong>Sushubh Mittal</strong>,</p>
<p dir="auto"><strong>Unfortunately</strong>, I think that this behaviour is a <strong>side-effect</strong> of the <strong>Proper Case</strong> capitalization rule itself :-((</p>
<p dir="auto">Have a look to my post, about the <strong>different capitalization</strong> rules, below :</p>
<p dir="auto"><a href="https://notepad-plus-plus.org/community/topic/130/convert-case-to/4" rel="nofollow ugc">https://notepad-plus-plus.org/community/topic/130/convert-case-to/4</a></p>
<p dir="auto">With the <strong>Start Case / Proper Case</strong> rule, <strong>ALL</strong> the words are <strong>capitalized</strong>, regardless its <strong>grammatical</strong> category. And, as the <strong>apostrophe</strong> sign is NOT a word character, the final <strong>lowercase</strong> letter <strong>s</strong>, of your example, is considered as a <strong>word</strong> ( containing <strong>only 1</strong> letter ), which is <strong>capitalized</strong> !</p>
<p dir="auto">There are <strong>plenty</strong> of examples, similar to yours, which give <strong>weird</strong> results, while applying the <strong>Proper Case</strong> rule</p>
<p dir="auto">Just consider the following word or sentences :</p>
<pre><code>McDonald
MacDonald
O'Neil
Google's
A FBI Inspector
my.email@test.com
John Smith III
</code></pre>
<p dir="auto">Using the <strong>TextFX - TextFX Characters - Proper Case</strong>, on that <strong>selected</strong> text , you’ll get :</p>
<pre><code>Mcdonald
Macdonald
O'Neil
Google'S
A Fbi Inspector
My.Email@Test.Com
John Smith Iii
</code></pre>
<p dir="auto">You’ll, also, get the <strong>same</strong> results, if you perform the <strong>regular</strong> expression search and replace, given, on my post, referred above, for the <strong>Proper Case</strong> capitalization rule :</p>
<p dir="auto">SEARCH = <strong><code>(\w)(\w*)</code></strong> and REPLACE = <strong><code>\u\1\L\2</code></strong></p>
<p dir="auto">It’s easy to understand that the <strong>only</strong> way to get the <strong>good</strong> spelling for <strong>all</strong> these cases, would require an <strong>artificial intelligence engine</strong>, which would be able to know that :</p>
<ul>
<li><strong>MacDonald</strong> is <strong>legal</strong> denomination of a restaurant</li>
<li><strong>FBI</strong> is an abbreviation of <strong>Federal Bureau of Investigation</strong></li>
<li>An <strong>E-mail</strong> address NEVER contains any <strong>uppercase</strong> letter</li>
<li>The characters <strong>III</strong>, after a <strong>proper</strong> name, is a <strong>Roman</strong> number</li>
</ul>
<p dir="auto">and so on…</p>
<p dir="auto">Moreover, how to distinguish, for instance, between the Scottish name <strong>O’Neil</strong> and the name <strong>Google’s</strong>, when applying the <strong>Proper Case</strong> rule ?</p>
<p dir="auto">However, IF you prefer that your text <strong>doesn’t</strong> contain any <strong>uppercase</strong> letter, right after an <strong>apostrophe</strong> sign, here is, below, a <strong>S/R</strong> which could achieve the <strong>Proper Case</strong> rule, while including that <strong>specific</strong> rule :</p>
<p dir="auto">SEARCH = <strong><code>(\w|')(\w*)</code></strong> and REPLACE = <strong><code>\u\1\L\2</code></strong></p>
<p dir="auto">So the <strong>two</strong> sentences :</p>
<pre><code>The different Google's applications
The name O'Neil is very common, in Scotland
</code></pre>
<p dir="auto">then, would become :</p>
<pre><code>The Different Google's Applications
The Name O'neil Is Very Common, In Scotland
</code></pre>
<p dir="auto">With the hope that this post helps you, a bit !</p>
<p dir="auto">Best Regards,</p>
<p dir="auto">guy038</p>
]]></description><link>https://community.notepad-plus-plus.org/post/11521</link><guid isPermaLink="true">https://community.notepad-plus-plus.org/post/11521</guid><dc:creator><![CDATA[guy038]]></dc:creator><pubDate>Sun, 27 Sep 2015 09:37:36 GMT</pubDate></item></channel></rss>