You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run into this apostrophe issue in almost all of my requests, particularly when I am typing them out on mobile, but that may be more due to me just using it more on mobile than desktop.
It looks like was referenced in #1353 but it felt reasonable to open a new issue on this specifically.
Most often it’s autocorrect formatting the apostrophe as ‘ by default, and not necessarily more/less prominent for me whether I’m using mobile or desktop apps, browsers, or something like my iOS Shortcuts app for passing text commands to Assist. And this is mostly the same for iOS or macOS dictation inputs in the same spots.
Many of the areas and devices I have belong to “someone” so the possessive is used in the majority of the entity names being interacted with through Assist.
Ideal world:
The area called "Kyle's Office" (non-curly apostrophe) would be recognized when input is any iteration of apostrophes:
Kyle's Office
Kyle’s Office
Kyles Office
This feels like a small-but-important case to handle for the people in my home that would be willing to learn specific incantations for wording these requests, but they would be put off by having to take into account different types of punctuation for a request that’s otherwise well-formed (i.e., this would be a pretty large barrier to folks who doesn’t want to “deal” with knowing the single quote style of ‘ vs ' in their requests, nor having to think about the inconsistencies when naming or re-naming their new entities using different styles).
The text was updated successfully, but these errors were encountered:
kylehakala
changed the title
Apostrophe type must match same style in name area/entity/etc.
Apostrophe type must match same style in name of area/entity/etc.
Mar 15, 2024
I run into this apostrophe issue in almost all of my requests, particularly when I am typing them out on mobile, but that may be more due to me just using it more on mobile than desktop.
It looks like was referenced in #1353 but it felt reasonable to open a new issue on this specifically.
Most often it’s autocorrect formatting the apostrophe as ‘ by default, and not necessarily more/less prominent for me whether I’m using mobile or desktop apps, browsers, or something like my iOS Shortcuts app for passing text commands to Assist. And this is mostly the same for iOS or macOS dictation inputs in the same spots.
Many of the areas and devices I have belong to “someone” so the possessive is used in the majority of the entity names being interacted with through Assist.
Ideal world:
The area called "Kyle's Office" (non-curly apostrophe) would be recognized when input is any iteration of apostrophes:
This feels like a small-but-important case to handle for the people in my home that would be willing to learn specific incantations for wording these requests, but they would be put off by having to take into account different types of punctuation for a request that’s otherwise well-formed (i.e., this would be a pretty large barrier to folks who doesn’t want to “deal” with knowing the single quote style of ‘ vs ' in their requests, nor having to think about the inconsistencies when naming or re-naming their new entities using different styles).
The text was updated successfully, but these errors were encountered: