Localize the issue due date events

[yardenshoham]

• Follows Use auto-updating, natively hoverable, localized time elements #23988

Before

After

[yardenshoham]

I really don't like the way I had to mess with the dictionary files, is there any way to avoid this?

I tried

@@ -295,7 +295,7 @@
                                {{template "shared/user/avatarlink" dict "Context" $.Context "user" .Poster}}
                                <span class="text grey muted-links">
                                        {{template "shared/user/authorlink" .Poster}}
-                                       {{$.locale.Tr "repo.issues.due_date_added" .Content $createdStr | Safe}}
+                                       {{$.locale.Tr "repo.issues.due_date_added" (template "shared/datetime/short" (dict "Datetime" .Content "Fallback" .Content)) $createdStr | Safe}}
                                </span>

but apparently that's illegal...

[delvh]

I can only see one suitable solution that will take some refactoring:
Add a method Comment.AsTimeStamp() that only works on comments with the correct comment types where the content of the comment is a timestamp in string form.
Then, you can call .AsTimeStamp().TimeSinceUnix().
You may even decide to panic in this new method instead of throwing an error as it can only happen when someone calls this method in the wrong place.

[wxiaoguang]

It could be like this:

{{$s := printf "<relative-time ...>" ....}}

Then pass the $s to Tr

[wxiaoguang]

It's better not to do so. At least, wait for a proper i18n system (with correct datetime support)

• [Proposal] Use ICU message for i18n & l10n #23863