Comments (33)
Maybe we should also use a more mature format like gettext? :)
from gitea.
@tboerger we need a colaborative platform to be easy to any Gitea collaborator help and we manage, like Weblate, Pootle and Zanata or Crowdin.
from gitea.
This sound suggestive 👍
https://github.com/anthonynsimon/parrot
from gitea.
Parrot is pretty chaotic to setup, weblate doesn't directly support the ini format, so I have requested an OSS project on Crowdin and it have already been approved: https://crowdin.com/project/gitea
from gitea.
My take on this is more related to backend than frontend.
Keep all translation-files in a separate repo (subtree for pulling into Gitea).
Pros:
- Each new translation-update can be done as a separate branch, without having to rebase on gitea-updates every 5 minutes.
- Each branch can be spun up as a separate container on gitea.io for easy testing (e.g. new_branch.translate.gitea.io)
- If new translations are added in en_US on master, you can easily rebase without having to update Gitea (less error prone at least)
- Translation-tools that speak git (e.g. Weblate ) can be used without fscking around with the gitea history
Cons:
- Someone has to merge the translations back into Gitea when they are mainlined
Feel free to pitch in on pros/cons for this, as this list is very biased and I can't really find any cons 😕
from gitea.
Sounds like reinventing the wheel to me. This is what specialized translation code does.
from gitea.
I really like the idea if the tool is kept simple, yet I still don't know if that should be port of gitea.
from gitea.
@lunny this Idea is good, but Gitea will lose standard among all installations, since the user will be able to customize your translations. With this, I think that will be more hard to we understand and solve possible issues about UI.
from gitea.
So we have to assign language tanslation maintainer for LGTM locale file PRs.
from gitea.
@lunny Then I think that's the way it's better.
Option to change translations, a big alert stating that the layout may break if you do not use the feature with care and a resource displaying when local translation isn't default from Gitea.
Whit this I think we can avoid possible issues as this
"Problem with right menu #114"
"
Guys, my menu is bigger and ugly, I'm opening this issue to solve this
"
from gitea.
@lunny ah, other problem, will be more easy to use translation on admin to XSS, because current translations have some html elements. A not a nice person can put similar to <script>getMy(document.cookie)</script>
as example. On specialized tools is more easy to translate and manager translations to avoid this problems.
from gitea.
Hi, I think that's great! Users should control the size of name themselves.
from gitea.
When ins't defined this question, isn't good idea at least change manually on files from Gogs
to Gitea
for first release?
from gitea.
I remember @tboerger has sent a request to Weblate?
from gitea.
https://weblate.org/en/hosting/ @tboerger has you apply on this?
from gitea.
from gitea.
We could host weblate on our own server
from gitea.
from gitea.
If we cannot received the response some days, we could consider host it on our server.
from gitea.
It was already discussed and proposed, so yes. Considering it.
from gitea.
So let's setup parrot and close this issue? @tboerger @bkcsoft any idea?
from gitea.
Parrot doesn't support the ini format, so we most use weblate or something else
from gitea.
@tboerger Are you sure it doesn't?
from gitea.
@tboerger Are you sure it doesn't?
Yes, I'm sure: https://github.com/anthonynsimon/parrot/tree/master/parrot-api/export
from gitea.
It seems the interface is simple so that we can write an ini one using the same library with Gitea's configuration using.
from gitea.
It seems the interface is simple so that we can write an ini one using the same library with Gitea's configuration using.
That sounds good, so somebody should do that and we will see how long it takes to get accepted. But beside that I personally prefer MariaDB, this supports only PostgreSQL.
from gitea.
And maybe we should move this to v1.2?
from gitea.
Does crowdin has an API?
from gitea.
Of course it got
from gitea.
So how should we copy TRANSLATION back to this repository?
from gitea.
I'll look at integrating this during the weekend.
Seems like I need 2 commands, push and pull.
push
- on merge
master
check if translations are updated - upload to CrowdIn
pull
- check if translations have been updated
- pull changes from CrowdIn
- add, commit, push, create PR (why of course, nothing gets in w/o reviews 😂 )
from gitea.
further extension on push
is if a translation other than en_US is changed
- pull
- apply change
- if no merge-conflicts, add,commit,merge,PR
from gitea.
I probably won't have time to check this in the near future
from gitea.
Related Issues (20)
- frp + nginx reverse proxy + ssl = push 403 HOT 6
- AutoSignIn: permission denied --> HTTP 500 HOT 5
- Gitea reverse proxy authentication problems.
- Sort type Newest for isues/pull request is not working
- Flake test: `TestWorkerPoolQueueWorkerIdleReset` HOT 1
- ENABLE_GZIP activated will result in tar.gz & tgz files compressed 2 times in gzip HOT 3
- comparison api unable to calculate the difference between the commit IDs HOT 1
- Can not create merge commit when checks succeed HOT 1
- Slow response on repo/search
- Automatically restart runner after a crash HOT 2
- Checkbox offset on settings -> application page
- UI border-radius inconsistent problems HOT 1
- Merged/Closed PR should not be approvable or request changes in diff page?
- Job will be frozen when stop the runner after job success
- setup gitea as oauth idP behind nginx sub-path fail HOT 6
- Consider relaxing access constraints on `/api/users/{username}/keys` HOT 3
- Project board column abel visual bug
- New pull request imagediff js error HOT 4
- Pull request search shows merged PRs in Open tab HOT 4
- Reproducible builds and strict dependency verification HOT 13
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gitea.