32
41
Fork
You've already forked website
52

WIP: internationalisation #57

Closed
caesar wants to merge 4 commits from caesar/forgejo-website:wip-i18n into main
pull from: caesar/forgejo-website:wip-i18n
merge into: forgejo:main
forgejo:main
forgejo:monthly-2026-05
forgejo:mahlzahn-eslint-js
forgejo:preview-link-status
forgejo:nightfire
forgejo:2022年12月14日-main
Member
Copy link

I started work on this a couple of weeks back and haven't had the time to come back to it. I'm pushing it here so people can give input or potentially someone else can continue work on it if I don't get time. (But let me know so we don't duplicate work.)

The locale JSON files are supposed to be compatible with Weblate.

I don't think it will make sense to use Weblate for long-form text (blog posts etc), but I haven't tried yet.

I should also apologise for what I'm sure are horrible Spanish translations, I just needed some placeholder translations 😆

I started work on this a couple of weeks back and haven't had the time to come back to it. I'm pushing it here so people can give input or potentially someone else can continue work on it if I don't get time. (But let me know so we don't duplicate work.) The locale JSON files are supposed to be compatible with Weblate. I don't think it will make sense to use Weblate for long-form text (blog posts etc), but I haven't tried yet. I should also apologise for what I'm sure are horrible Spanish translations, I just needed some placeholder translations 😆
First-time contributor
Copy link

I promise to do a Spanish review asap. But i think is enough for now if you want merge it.
Now I am out of pc.

I promise to do a Spanish review asap. But i think is enough for now if you want merge it. Now I am out of pc.
Author
Member
Copy link

Thanks @fsologureng , it's far from being ready to merge anyway so I'm sure there'll be time for you to contribute to a proper Spanish localisation. I haven't even internationalised all the strings yet anyway, nor set up weblate, so there's a long way to go.

Thanks @fsologureng , it's far from being ready to merge anyway so I'm sure there'll be time for you to contribute to a proper Spanish localisation. I haven't even internationalised all the strings yet anyway, nor set up weblate, so there's a long way to go.
First-time contributor
Copy link

There is an agreement about reader treatment? 2nd person or 3rd person?
you can be translated to Spanish as 2nd person or 3rd person in some contexts.

(I put this comment initially in other issue totally unrelated, merging desktop windows XD)

There is an agreement about reader treatment? 2nd person or 3rd person? `you` can be translated to Spanish as 2nd person or 3rd person in some contexts. (I put this comment initially in other issue totally unrelated, merging desktop windows XD)
First-time contributor
Copy link

@caesar, I tried a PR to your fork but couldn't :/ fsologureng/website@2c983503f2

@caesar, I tried a PR to your fork but couldn't :/ https://codeberg.org/fsologureng/website/commit/2c983503f28172505f125533771dbbc0cc37c9a6
Author
Member
Copy link

@fsologureng that's strange, what happens when you try to create the PR?
Anyway I can pull your commit directly and merge it locally, no problem. Thanks for the corrections.

There is an agreement about reader treatment? 2nd person or 3rd person?
you can be translated to Spanish as 2nd person or 3rd person in some contexts.

In English there's only one option, second person.

For other languages I think it's a per-language choice depending on language conventions. Of course a regional choice could also make sense but I'm not sure if we really need regional localisations at this point.

  • In Spanish for example I suppose you are referring to "usted", the formal "you" which takes third-person singular conjugations of verbs. In the case of Spanish my feeling is to stick with the informal "tu", though obviously the opinions of native speakers such as yourself are more relevant.

  • Portuguese is another interesting case, where there is a major regional difference: In Brazil, "você" is used as the primary second-person pronoun but it takes third-person verb conjugations. In Portugal on the other hand "tu" is used which takes second-person verb conjugations.

  • French is another interesting case. My French is poor, so @dachary should correct me if I'm wrong, but I understand that their second -person singular formal pronoun "vous" is identical to the second-person plural and takes second-person plural verb conjugations.

For all these reasons it's not an easy thing to have a generic rule about that would apply to all locales.

That said, my own feeling is we should tend towards informal rather than formal, but there may be locales where this is not appropriate.

@fsologureng that's strange, what happens when you try to create the PR? Anyway I can pull your commit directly and merge it locally, no problem. Thanks for the corrections. > There is an agreement about reader treatment? 2nd person or 3rd person? > `you` can be translated to Spanish as 2nd person or 3rd person in some contexts. In English there's only one option, second person. For other languages I think it's a per-language choice depending on language conventions. Of course a regional choice could also make sense but I'm not sure if we really need regional localisations at this point. - In Spanish for example I suppose you are referring to "usted", the formal "you" which takes third-person singular conjugations of verbs. In the case of Spanish my feeling is to stick with the informal "tu", though obviously the opinions of native speakers such as yourself are more relevant. - Portuguese is another interesting case, where there is a major regional difference: In Brazil, "você" is used as the primary second-person pronoun but it takes third-person verb conjugations. In Portugal on the other hand "tu" is used which takes second-person verb conjugations. - French is another interesting case. My French is poor, so @dachary should correct me if I'm wrong, but I understand that their second -person singular formal pronoun "vous" is identical to the second-person *plural* and takes second-person plural verb conjugations. For all these reasons it's not an easy thing to have a generic rule about that would apply to all locales. That said, my own feeling is we should tend towards informal rather than formal, but there may be locales where this is not appropriate.
First-time contributor
Copy link

@fsologureng that's strange, what happens when you try to create the PR?
Anyway I can pull your commit directly and merge it locally, no problem. Thanks for the corrections.

$ git push caesar-origin HEAD
Enumerando objetos: 15, listo.
Contando objetos: 100% (15/15), listo.
Compresión delta usando hasta 8 hilos
Comprimiendo objetos: 100% (8/8), listo.
Escribiendo objetos: 100% (9/9), 2.26 KiB | 2.26 MiB/s, listo.
Total 9 (delta 5), reusados 0 (delta 0), pack-reusados 0
remote: 
remote: Gitea: User permission denied for writing.
To codeberg.org:caesar/forgejo-website.git
 ! [remote rejected] HEAD -> wip-i18n (pre-receive hook declined)
error: falló el push de algunas referencias a 'codeberg.org:caesar/forgejo-website.git'

It is very likely that I am doing something wrong. I'm improving my git skills but they are still insufficient for everything :)

> @fsologureng that's strange, what happens when you try to create the PR? > Anyway I can pull your commit directly and merge it locally, no problem. Thanks for the corrections. ~~~ $ git push caesar-origin HEAD Enumerando objetos: 15, listo. Contando objetos: 100% (15/15), listo. Compresión delta usando hasta 8 hilos Comprimiendo objetos: 100% (8/8), listo. Escribiendo objetos: 100% (9/9), 2.26 KiB | 2.26 MiB/s, listo. Total 9 (delta 5), reusados 0 (delta 0), pack-reusados 0 remote: remote: Gitea: User permission denied for writing. To codeberg.org:caesar/forgejo-website.git ! [remote rejected] HEAD -> wip-i18n (pre-receive hook declined) error: falló el push de algunas referencias a 'codeberg.org:caesar/forgejo-website.git' ~~~ It is very likely that I am doing something wrong. I'm improving my git skills but they are still insufficient for everything :)
First-time contributor
Copy link

@dachary: in case you feel comfortable to share your opinion, I have created a dedicated issue to comment on the topic #66.

@dachary: in case you feel comfortable to share your opinion, I have created a dedicated issue to comment on the topic #66.
Author
Member
Copy link

Ah, you're pushing directly to this branch in my fork, rather than sending a PR. I hadn't enabled that, but now it's enabled so you should be able to do that.

Ah, you're pushing directly to this branch in my fork, rather than sending a PR. I hadn't enabled that, but now it's enabled so you should be able to do that.
First-time contributor
Copy link

Ah, you're pushing directly to this branch in my fork, rather than sending a PR. I hadn't enabled that, but now it's enabled so you should be able to do that.

ups, that was not the idea :/

And I am not allowed to open PR neither (button disabled).

> Ah, you're pushing directly to this branch in my fork, rather than sending a PR. I hadn't enabled that, but now it's enabled so you should be able to do that. ups, that was not the idea :/ And I am not allowed to open PR neither (button disabled).
@ -0,0 +1,47 @@
{
"site": {
"title": "Forgejo Beyond coding. We forge.",
First-time contributor
Copy link

I'm getting some warnings for all the scripts in the local files, saying they are ambiguous unicode characters.

I'm getting some warnings for all the scripts in the local files, saying they are ambiguous unicode characters.
Author
Member
Copy link

The warning doesn't really affect anything – it's more relevant to code than to text. An em-dash (as used) is appropriate here, not a hyphen. If we want to avoid the warning in the Forgejo UI we could escape the em-dash as — I suppose.

The warning doesn't really affect anything – it's more relevant to code than to text. An em-dash (as used) is appropriate here, not a hyphen. If we want to avoid the warning in the Forgejo UI we could escape the em-dash as `—` I suppose.
fsologureng marked this conversation as resolved
First-time contributor
Copy link

Ah, you're pushing directly to this branch in my fork, rather than sending a PR. I hadn't enabled that, but now it's enabled so you should be able to do that.

I did it and it shows a CI commit not merged to the branch, is that the problem? I preferred not to do anything else.

> Ah, you're pushing directly to this branch in my fork, rather than sending a PR. I hadn't enabled that, but now it's enabled so you should be able to do that. I did it and it shows a CI commit not merged to the branch, is that the problem? I preferred not to do anything else.
Author
Member
Copy link

It seems fine to me @fsologureng, I am seeing the commit in the Git tree correctly.

Good idea to also cherry-pick the CI branch preview commit. I assume this PR can now be previewed at https://forgejo.codeberg.page/@pull_57/, but Codeberg Pages seems to be down at the moment so I can't check.

It seems fine to me @fsologureng, I am seeing the commit in the Git tree correctly. Good idea to also cherry-pick the CI branch preview commit. I assume this PR can now be previewed at https://forgejo.codeberg.page/@pull_57/, but Codeberg Pages seems to be down at the moment so I can't check.
Contributor
Copy link

closing as very out dated

closing as very out dated

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
404
Broken links or missing content
Accessibility
Accessibility
Blog post
Documentation
Forgejo Documentation
Internationalisation
i18n and l10n
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/website!57
Reference in a new issue
forgejo/website
No description provided.
Delete branch "caesar/forgejo-website:wip-i18n"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?