--65ccbf48045140709faf8e4e58182b1d Content-Type: text/plain; charset="ascii" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit mpyne added a comment. In https://phabricator.kde.org/D4023#77304, @aacid wrote: > Can you as a native speaker confirm this theory i've heard? > > If we are on "Monday 16", "Next Wednesday" means "Wednesday 25" if you want "Wednesday 18" you should say "This Wednesday" Yes, if you are on a Monday the 16th, the immediate next Wednesday (18th) would generally be referred to as "this Wednesday" while the Wednesday following (25th) would be "next Wednesday". This might not be true for all English dialects though. E.g. en_GB seems to have the immediately following Wednesday (18th) as "Wednesday next", while the Wednesday after (25th) would "Wednesday week". However if the number of days between now and then is long enough then many people would still refer to the later date as "next" instead of "this". This is reflected in some other APIs. For instance I tried adding a new calendar entry to a Google-based account for "next Thursday" from today (Sunday) and it added it for 4 days from now instead of 11 days from now. However even when adding an entry for "next Monday" (i.e. tomorrow or 8 days from now), Google still chose tomorrow. As long as our behavior in the code is consistent there shouldn't be much problem with using "Next $day" even in en_US since we're used to computer outputs not being precisely reflective of natural speech, and even in the U.S. there are people who always use "Next $day" in their natural speech to refer to the immediately succeeding day. As a result, I would keep the current scheme (at least for en_US) since that way there's less "magic" needed for the user in trying to decode what date the computer is trying to refer to. REPOSITORY R244 KCoreAddons REVISION DETAIL https://phabricator.kde.org/D4023 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: mpyne, #frameworks, kde-i18n-doc, aspotashev, aacid Cc: aacid --65ccbf48045140709faf8e4e58182b1d Content-Type: text/html; charset="ascii" Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable View Revision=
mpyne added a comment.

In D4023#773= 04, @aacid wrote:

Can you as a native speaker confir= m this theory i've heard?

If we are on "Monday 16", "Next Wednesday" means &qu= ot;Wednesday 25" if you want "Wednesday 18" you should say &= quot;This Wednesday"

Yes, if you are on a Monday the 16th, the immediate next Wednesday (18th= ) would generally be referred to as "this Wednesday" while the We= dnesday following (25th) would be "next Wednesday".

This might not be true for all English dialects though. E.g. en_GB seems to have<= /a> the immediately following Wednesday (18th) as "Wednesday next"= ;, while the Wednesday after (25th) would "Wednesday week".

However if the number of days between now and then is long enough then m= any people would still refer to the later date as "next" instead = of "this". This is reflected in some other APIs. For instance I= tried adding a new calendar entry to a Google-based account for "next= Thursday" from today (Sunday) and it added it for 4 days from now ins= tead of 11 days from now. However even when adding an entry for "next= Monday" (i.e. tomorrow or 8 days from now), Google still chose tomorr= ow.

As long as our behavior in the code is consistent there shouldn't b= e much problem with using "Next $day" even in en_US since we'= ;re used to computer outputs not being precisely reflective of natural spee= ch, and even in the U.S. there are people who always use "Next $day&qu= ot; in their natural speech to refer to the immediately succeeding day.

As a result, I would keep the current scheme (at least for en_US) since = that way there's less "magic" needed for the user in trying = to decode what date the computer is trying to refer to.


REPOSITORY
R244 KCoreAddons

REVISION DETAIL
https://phabricator.kde.org/D4023<= /a>

EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/

To: mpyne, Frameworks, kde-i18n-doc, as= potashev, aacid
Cc: aacid
--65ccbf48045140709faf8e4e58182b1d--