L10N BUG: Incorrect Japanese strings for TB's Find/Search criteria for date, "is before" and "is after"

RESOLVED FIXED

Status

Mozilla Localizations
ja / Japanese
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: ISHIKAWA, Chiaki, Assigned: marsf)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
Hi,

I read in a Japanese BBS that the search criteria
for date
 - "is before" and
 - "is after"

have incorrect Japanese strings.

Well, the the current Japanese string bundle seems to have 
 - 次の日付以前 for "is before"
 - 次の日付以降 for "is after".

However, these translated strings suggest that the target interval INCLUDE the particular date.
But TB excludes the end date, i.e., the date at the terminal of the interval.
(If it includes it, the original English strings would have been
"is before or equal to", and
"is after or equal to".

Basically we should make a clear distinction of ">" and "=>", or
"<" and "<=".
 
I would suggest the following translations:
- 次の日付より前 for "is before"
- 次の日付より後 for "is after".

Words of caution: everyday language is not exact.
I am not surprised if some people still incorrectly assume
that the date at the end of the intended interval (finite, or infinite) are still included even with my slightly improved Japanese translation.
Someone who has a formal education of mathematics would make the fine distinction of the usage, but it may be a tall order to assume that.
So we may eventually have to use the Japanese equivalent of
"is before (not including the following date)", and
"is after (not including the following date)".
This would be a little lengthy and awkward. We will see.
(Or use the equivalent of "looking at the days starting the day BEFORE the following date" and "looking at the days starting the day AFTER the following date" which can be translated into rather short Japanese strings.
is after -> 次の日の翌日以降
is before -> 次の日の前日以前
but they do look rather awkward, too.

I could not figure out where the strings resides in comm-central (mxr did not find it?)

So I leave someone to create the new string bundle along the line of my first suggestion:
- 次の日付より前 for "is before"
- 次の日付より後 for "is after".

TIA

Updated

2 years ago
Component: Search → ja / Japanese
Product: Thunderbird → Mozilla Localizations
QA Contact: l10n-qa
Version: 45 Branch → unspecified
(Assignee)

Comment 1

2 years ago
I confirmed that current translations are incorrect.

Ishikawa-san, we cannot fix l10n of esr or released version. However it must be fixed on the beta 46.0.

The strings for comm-central is here:
http://hg.mozilla.org/l10n-central/ja/file/tip/mail/chrome/messenger/search-operators.properties
http://hg.mozilla.org/l10n-central/ja-JP-mac/file/tip/mail/chrome/messenger/search-operators.properties
Assignee: nobody → chimantaea_mirabilis
Status: NEW → ASSIGNED
(In reply to Masahiko Imanaka [:marsf] from comment #1)
> I confirmed that current translations are incorrect.
> 
> Ishikawa-san, we cannot fix l10n of esr or released version. However it must
> be fixed on the beta 46.0.
> 
> The strings for comm-central is here:
> http://hg.mozilla.org/l10n-central/ja/file/tip/mail/chrome/messenger/search-
> operators.properties
> http://hg.mozilla.org/l10n-central/ja-JP-mac/file/tip/mail/chrome/messenger/
> search-operators.properties

Friendly reminder: do not land on central, land on aurora ;-)

Also note that 46 is going to ship next week, you should land it on aurora and request a new sign-off
(Assignee)

Comment 3

2 years ago
(In reply to Francesco Lodolo [:flod] from comment #2)
> Friendly reminder: do not land on central, land on aurora ;-)
> 
> Also note that 46 is going to ship next week, you should land it on aurora
> and request a new sign-off

OK, thanks.
(Assignee)

Comment 4

2 years ago
Fixed on aurora.

http://hg.mozilla.org/releases/l10n/mozilla-aurora/ja/rev/33f3f64419fa
http://hg.mozilla.org/releases/l10n/mozilla-aurora/ja-JP-mac/rev/b751f21caf3d
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED

Comment 5

2 years ago
FYI there won't be a 46 beta - it will be skipped. Next beta is planned to be 47
You need to log in before you can comment on or make changes to this bug.