Please be more careful at en-ja translation.

Please be more careful at en-ja translation.

Hello, I wish you will keep en-ja translation, and may I suggest with a bit of care to the essential details please?

  1. Do not omit numericals: the original sentence in en reads: "Total %1 {{PLURAL:%1|page|pages}} redirected to this page". While ja does not apply plurals, you need to keep singulars.
  2. Please do not add stopping period 「。」, which is not in the original en sentence in this case.

If you are tired, a short rest will be nice to yourself and your readers. Kindly,

Omotecho (talk)19:47, 4 December 2022

Do you know that Cejs is a project originally created and maintained in Japanese and Chinese (by a native speaker)? That's why the message was imported directly in Japanese and Chinese, and actually not translated on translatewiki.net. Otherwise the English version is actually their translation (and sometimes needs fixing by reporting bugs to them): Japanese and Chinese are the effective originals from the project itself.

  1. And anyway there was NO omission of the %1 in English, Japanese and Chinese, so nothing wrong (even if there was no "PLURAL" indication in the original Japanese or Chinese, because it was not necessary and not really required; but it was present in the English translated "source").
  2. If the Japanese or Chinese creator wanted to use a final period, that's fine, even if it may be suppressed in English. Many languages prefer using final dots at end of normal sentences (because these are not titles), even if they are not necessary "verbal" (in this case you can translate using a full verbal sentence if it looks better than a nominal phrase)!
Verdy p (talk)20:08, 4 December 2022

Hello, Verdy p, that is a very interesting notion: please include in your vantage both decent translators and those, like myself, who are pinged by the system that "something needs to be fixed" and come to check. Why do we/the system offer us to work on ja-en translation, offered to en-ja translation, then the system finds short comings? What are we doing ja-en-ja translation, which for sure ends up twisting what the original writer intended to?

It does not look fair to me as long as, you know, originals written in en will never suffer this kind of waste of time.

  1. Where do we place our readers?
  2. Who screens what to offer on this system? Don't they spend time as you did to find which was the original language, which should not be added into target/output language?
  1. How do you advise we make a template or some means so that we safely detour translating the original-translation original?

The whole system we rely on is trusted providing universal knowledge, and I wish it does not undermine our effort to realize our hope and ideology. Cheers,

Omotecho (talk)12:31, 27 December 2022
 

Thank you for the reminder. I will pay more attention. If there are any mistakes, please feel free to correct them, thank you.

Kanashimi (talk)00:30, 6 December 2022

May be the doc may say that the Japanese version is the actual original. This does not mean that Japanese or English cannot be fixed, but that the original project manager should be notified directly, using their support contact listed on the Project page. Not that the project seems lso to manage the Chinese version (not sure if thisi sin, traditional or Simplified Chinese), possibly by some other memebers of their developer team. We don't have lot of communciation from them, jsut some comments in their repository. This project has a very small team, and not used in lot of places, so may be they woudl welcome some help, and suggestions, possibly some additional developers. However we cannot decide for them here.

Verdy p (talk)15:28, 27 December 2022