[steinchen]

Originally Posted by Ephemerality

• /c - Characters are usually case-insensitive, this will make it sensitive. Good for terms that might show up and falsely match in other contexts. e.g. a character named Summer would incorrectly match on 'summer'.
• Example: Khal Drogo|/i,Drogo

Hi, just tried v2.0.10 GUI and it's working great. But I have a little problem with case sensitive names on my PW3.
First I built an alias file without any parameters. The file worked but "Will" was suddenly the most important character in "A Game of Thrones". So I searched and found the /c parameter. Building the xray file still works but my kindle still shows every "Will" and "will", the same happens for "Ned" Stark and others.
Does the Kindle cache the definitions somewhere or is there maybe a problem with the case sensitive parameter? By the way, the preview in the builder shows the same number of mentions as below.
I'm using a .mobi file, as it didn't find any chapters in my .azw3.
Here are some examples:

• Alias: Eddard Stark|/c,Eddard,Ned
  Count of mentions: 1988
  Right mention: Lord Eddard Stark dismounted and his ward...
  Wrong mention: There are things to be learned even from the dead.
• Alias: Will|/c
  Count of mentions: 768
  Right mention: Will saw them
  Wrong mention: We will find these men.
• Alias: Robert Baratheon|/c,Robert,Rob
  Count of mentions: 764
  Right mention: "For Robert!" he shouted.
  Wrong mention: At least as his wardrobe was concerned.

And as a feature suggestion: What do you think about a switch to only search for full words? Usefull for short names like Ned or Arry (so it wouldn't find turned and parry).