Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

@ChiahongHong @yuyinws @DotnetChen Please review

@adityatelange I had review this PR, It's correct and can be merged.

@DejavuMoe can we include #914 as well with this

@DejavuMoe can we include #914 as well with this

I think #914 should not have much effect on Chinese translation.

In Chinese (either Simplified or Traditional Chinese), the previous or next button on a page and post should be different terms, and I think they should be translated separately, for example

For Pages

• Previous and Next
• 上一页 和 下一页

For Posts

• Previous or Next
• 上一篇 和 下一篇

🧐Any suggestions? Please~

@ChiahongHong @yuyinws @DotnetChen

@DejavuMoe @adityatelange
I think the better way is add two new keywords in i18n file to distinguish Page and Post. like this:

# en.yaml
- id: prev_page
  translation: "Prev"
- id: next_page
  translation: "Next"
- id: prev_post
  translation: "Prev"
- id: next_post
  translation: "Next"

In Chinese, It will be translated like this:

- id: prev_page
  translation: "上一页"
- id: next_page
  translation: "下一页"
- id: prev_post
  translation: "上一篇"
- id: next_post
  translation: "下一篇"

@DejavuMoe @adityatelange I think the better way is add two new keywords in i18n file to distinguish Page and Post. like this:

# en.yaml
- id: prev_page
  translation: "Prev"
- id: next_page
  translation: "Next"
- id: prev_post
  translation: "Prev"
- id: next_post
  translation: "Next"

In Chinese, It will be translated like this:

- id: prev_page
  translation: "上一页"
- id: next_page
  translation: "下一页"
- id: prev_post
  translation: "上一篇"
- id: next_post
  translation: "下一篇"

@adityatelange @yuyinws
Yes, I think it's a good way, totally agree with the way #892 updated the translation.

How about we just have translations for 'next and previous' instead of 'next_page/next_post'? I hope that is doable.
The more translations more PRs harder will it be to maintain.
Although it already was next_page and never next_post, I think it will be fine if ee keep it as it is, if that's not a problem.

How about we just have translations for 'next and previous' instead of 'next_page/next_post'? I hope that is doable. The more translations more PRs harder will it be to maintain. Although it already was next_page and never next_post, I think it will be fine if ee keep it as it is, if that's not a problem.

Mmmm, in Chinese, a separate next and previous should be a bit strange. But using next_page/next_post would indeed make the current i18n project more difficult (until all languages get updated contributions in time, otherwise it might break the current translations for some languages)

And the semantics of next_page should be stronger than next_post in Chinese, so I only updated the translation of previous_page - next_page in my PR, which is acceptable.