Treat different capitalizations as unique names

[kbs666]

I explained it in real terms and I've explained it simply. I do not know what else to say to make it clear to you.

[kbs666]

!

Yes, it would! I do not understand why this is so hard to make clear. Your proposal is that every capitalization form of any string be a distinct name. That means that ignoring case would no longer possible, at all! AB would not match ab ever under any circumstance. They are separate names! To make my existing topic work, and that is just one example, would need at minimum 2 additional aliases. Which would require me, and every other person affected to go back through and add those aliases to every topic with no idea which are affected and which are not until something fails to link. And lord help the people who have case matching set to auto correct. Just so you can use auto accept, no thanks.

[Randall Jhen]

That... is not my proposal.

My proposal is to let a name with Case Matching set to Sensitive be distinct from another identically spelled but differently capitalized name with Case Matching also set to Sensitive.

A name with case matching set to None would still find every capitalization variant.

[kbs666]

Originally Posted by Randall Jhen

That... is not my proposal.

My proposal is to let a name with Case Matching set to Sensitive be distinct from another identically spelled but differently capitalized name with Case Matching also set to Sensitive.

A name with case matching set to None would still find every capitalization variant.

Which is exactly what I've written a bunch of times and is succinctly in your title. You want every capitalization of a token to be distinct from every other capitalization which breaks all my realms.

[Silveras]

Originally Posted by kbs666

Which is exactly what I've written a bunch of times and is succinctly in your title. You want every capitalization of a token to be distinct from every other capitalization which breaks all my realms.

Hmm .. maybe I see the issue here.

It sounds like what @kbs666 is afraid of is that the suggestion as worded in the title would make each Topic Name/alias globally unique within a Realm based on the capitalization. (ex. "The Green" and "The green" could only exist once each as a Topic name, and no aliases for any other topic could ever match those).

A literal reading of the topic title could be like that. The dozen or so follow-up attempts to explain that's not it seem to be failing to reach past that reading.

The request, putting aside the "uniqueness" wording, is for aliases to honor case-sensitivity when being added in the GUI. That's it. That's what it all boils down to. So if I see a need to add "The green" as a case-sensitive alias for a topic named "The Green" with case-sensitivity, that's all it is asking for. Right now, even if both are marked as case-sensitive, it treats them as case-insensitive and prevents the addition of the alias.

Auto-Accept is irrelevant.
Mass import is irrelevant.

I actually think that because case-sensitivity is selectable for the main name, true name, and aliases, it is a bug that it is not currently honored in the GUI when adding aliases.

[Silveras]

Ok, let's take a step back.

Currently, I can create multiple topics and give them same alias, with different capitalizations or the same capitalizations:

Topic 1 Main Name: "Topic 1", case-insensitive.
Topic 1 Alias: "Topic One", case-sensitive
Topic 1 Alias: "Topic 2", case-sensitive.
Topic 2 Main Name: "Topic 2", case-sensitive.
Topic 2 Alias: "Topic Two", case-insensitive
Topic 3 Main Name: "Topic 1", case-insensitive.
Topic 3 Alias: "Topic One", case-sensitive

The GUI will warn me that I am re-using a name without a suffix to differentiate, but one of the options is "Save anyway" (amounting to a response of 'I understand, do it anyway'). This will cause the the GUI to stop and request that I select which Topic text of "Topic 2" should link to, as there are two match candidates. Likewise, text of "Topic 1" would present two possible matches.


What I cannot do is this:
Topic 1 Main Name: "Topic One" , case-sensitive
Topic 1 Alias: "Topic one", case-sensitive. <-- THIS IS NOT ALLOWED

Regardless of the case sensitivity settings, the alias is seen as a case-insensitive duplicate of the main name.

Because these aliases CAN be created across topics, I cannot see how honoring the case sensitivity of the aliases breaks anything in any way that is not already "broken" by allowing the aliases to exist on what amounts to the wrong topic. The only effect I can foresee is that there may be an additional match candidate suggested for certain text (which is exactly what I want).

[kbs666]

Each topic title and alias is a name. Names can point to multiple topics. Having the same name twice in one topic makes no sense.

What the op wants, and I'll repeat I've never ever seen a time where this is a good idea, is to create a topic with a common name and then use auto accept so he can do a mass import and not have to spend any time at the keyboard during the linking process.

I'm starting to wish that tool had never been created. It has resulted in multiple requests for features that would make life harder for people who enter their own data by hand.

[Randall Jhen]

Having two different case sensitive names in a topic makes sense when a topic name may be capitalized in some instances and not capitalized in others. Take, for instance, these examples:

1. The Green is renowned for its abundant, explosive life.
2. Settlements are hard to find in the Green, because whole forests may spring forth from the ground overnight.

Linked topic name: Green Sun
Linked topic alternate name: The Green (case sensitive)

This name combination will capture example 1, but not example 2. If I add "the Green" (case sensitive), in an effort to capture examples 1 and 2, the OK button is grayed out.

Also, I'm not using an import tool. I'm copy-pasting from a PDF. And this isn't about auto-accepting links; it's about preventing false positives.

Silveras, thank you for understanding and explaining my meaning.

[kbs666]

Originally Posted by Randall Jhen

Having two different case sensitive names in a topic makes sense when a topic name may be capitalized in some instances and not capitalized in others. Take, for instance, these examples:

1. The Green is renowned for its abundant, explosive life.
2. Settlements are hard to find in the Green, because whole forests may spring forth from the ground overnight.

Linked topic name: Green Sun
Linked topic alternate name: The Green (case sensitive)

This name combination will capture example 1, but not example 2. If I add "the Green" (case sensitive), in an effort to capture examples 1 and 2, the OK button is grayed out.

Also, I'm not using an import tool. I'm copy-pasting from a PDF. And this isn't about auto-accepting links; it's about preventing false positives.

Silveras, thank you for understanding and explaining my meaning.

Why include the article at all? Your entire problem is that you have added something to the name that doesn't need to be there.

If you were not doing a mass import then this wouldn't be an issue. Clicking ok few times per article is nothing.

[Randall Jhen]

Originally Posted by kbs666

Why include the article at all? Your entire problem is that you have added something to the name that doesn't need to be there.

If you were not doing a mass import then this wouldn't be an issue. Clicking ok few times per article is nothing.

I include the article because I don't want every instance of the words silver, blue, green, indigo, grey, pale, red, gold, and invisible to prompt for a link; the Silver, the Blue, the Green, etc. are rarer and won't capture adjectives when I'm looking for nouns. Except when "the" is capitalized at the start of a sentence, at which point link detection skips the reference because the case doesn't match.