Sitelet https://web.archive.org/web/20201015131320/https://github.com/go-gitea/gitea/issues/13123
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Description for issues.ref_closing_from ambiguous and incorrectly localized #13123

Open
qwertfisch opened this issue Oct 12, 2020 · 6 comments
Open

Comments

@qwertfisch
Copy link

@qwertfisch qwertfisch commented Oct 12, 2020

  • Gitea version (or commit ref): 1.12.3
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

After a pull request is added by a user and linked to an issue, the following reference is then described in the given format:

user referenced a pull request that will close this issue time of reference

A specific example would be:

qwertfisch referenced a pull request that will close this issue 1 week ago

Ways of reading

  1. The meaning of it, as I understand, is that a user has referenced a pull request 1 week ago, and this pull request will (at some other time in the future) close this issue.
  2. But the actual reading tells me that a user referenced a pull request, and this pull request will close this issue 1 week ago (which doesn’t make any sense, at least for me).

This is quite ambiguous. Even more so in German, which clearly is translated unambiguously by the second form (considering the position of the comma and the date inside the subordinate clause).

qwertfisch hat auf einen Pull Request verwiesen, welcher das Issue vor 1 Woche schließen wird

Unfortunately English does not enforce commas and also puts the date at the end of the sentence.

Screenshots

scr_20201013-002146
scr_20201013-002200

Possible solution

I am not sure if this is a definitive bug or just an ambiguous way of reading (for English). At least the German translation should be changed to not represent the second form semantically.

An umambiguous reading could be something like this:

qwertfisch has referenced a pull request 1 week ago, that will close this issue

This way only the part “has referenced a pull request” can be an href link, not the text “that will close this issue” after the date. This behaviour is already present at the incorrect German translation, where “schließen wird” (after the date) is just text, not an href.

@6543
Copy link
Member

@6543 6543 commented Oct 12, 2020

solution: fix template to: add a check if time is in the past ... if true, use new translation strings <- has to be added

@qwertfisch
Copy link
Author

@qwertfisch qwertfisch commented Oct 13, 2020

The date will always be in the past because it references the date when the pull request was added.

@6543
Copy link
Member

@6543 6543 commented Oct 13, 2020

oh missed that ... then it's easy: fix the english translation by creating a pull and the rest is done via crowdin

@ivanvc
Copy link
Contributor

@ivanvc ivanvc commented Oct 15, 2020

Rather than changing the ordering of the words, I think a good solution would be maybe adding a hyphen before the time of reference.

i.e.

user referenced a pull request that will close this issue – time of reference
qwertfisch referenced a pull request that will close this issue – 1 week ago

But then, this will mean that many actions that have the time reference at the end would need an update, not just the reference to the pull request. Does this sound like something feasible? I can do the PR to address this. Just want to know this sounds like the correct decision (cc. @6543)

@zeripath
Copy link
Contributor

@zeripath zeripath commented Oct 15, 2020

I think adding an em-dash — (U+2014) (not hyphen) would be a good idea

@eneuschild
Copy link
Contributor

@eneuschild eneuschild commented Oct 15, 2020

I've been thinking the same thing as @ivanvc. The English version is ambiguous, yes, but not a bad wording per se. Visually setting off the date string rather than incorporating it into the sentence looks to me like a good way to resolve the ambiguity and also make sure that date strings can be at the end of the message in all languages alike.

I have also suggested a correction of the faulty German translation on Crowdin, which still needs to be reviewed there. Let's see how quick they are. ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.