Translation process #44

@strk commented on GitHub (Nov 8, 2016):

Sounds like reinventing the wheel to me. This is what specialized translation code does.

@strk commented on GitHub (Nov 8, 2016): Sounds like reinventing the wheel to me. This is what specialized translation code does.

GiteaMirror commented

@metalmatze commented on GitHub (Nov 8, 2016):

I really like the idea if the tool is kept simple, yet I still don't know if that should be port of gitea.

@metalmatze commented on GitHub (Nov 8, 2016): I really like the idea if the tool is kept simple, yet I still don't know if that should be port of gitea.

GiteaMirror commented

@joubertredrat commented on GitHub (Nov 8, 2016):

@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.

@joubertredrat commented on GitHub (Nov 8, 2016): @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.

GiteaMirror commented

@lunny commented on GitHub (Nov 8, 2016):

So we have to assign language tanslation maintainer for LGTM locale file PRs.

@lunny commented on GitHub (Nov 8, 2016): So we have to assign language tanslation maintainer for LGTM locale file PRs.

GiteaMirror commented

@joubertredrat commented on GitHub (Nov 8, 2016):

@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

"

@joubertredrat commented on GitHub (Nov 8, 2016): @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 ![screenshot-repo](https://cloud.githubusercontent.com/assets/1520407/20097193/59d9c666-a594-11e6-8977-0634c9cd4856.png) "

GiteaMirror commented

@joubertredrat commented on GitHub (Nov 8, 2016):

@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.

@joubertredrat commented on GitHub (Nov 8, 2016): @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.

GiteaMirror commented

@lunny commented on GitHub (Nov 8, 2016):

Hi, I think that's great! Users should control the size of name themselves.

@lunny commented on GitHub (Nov 8, 2016): Hi, I think that's great! Users should control the size of name themselves.

GiteaMirror commented

@joubertredrat commented on GitHub (Nov 9, 2016):

When ins't defined this question, isn't good idea at least change manually on files from Gogs to Gitea for first release?

@joubertredrat commented on GitHub (Nov 9, 2016): When ins't defined this question, isn't good idea at least change manually on files from `Gogs` to `Gitea` for first release?

GiteaMirror commented

@bkcsoft commented on GitHub (Dec 2, 2016):

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 :trollface:

Feel free to pitch in on pros/cons for this, as this list is very biased and I can't really find any cons 😕

@bkcsoft commented on GitHub (Dec 2, 2016): 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](https://docs.weblate.org/en/latest/vcs.html#git) ) can be used without fscking around with the gitea history Cons: - Someone has to merge the translations back into Gitea when they are mainlined :trollface: Feel free to pitch in on pros/cons for this, as this list is very biased and I can't really find any cons :confused:

GiteaMirror commented

@tboerger commented on GitHub (Dec 2, 2016):

Maybe we should also use a more mature format like gettext? :)

@tboerger commented on GitHub (Dec 2, 2016): Maybe we should also use a more mature format like gettext? :)

GiteaMirror commented

@joubertredrat commented on GitHub (Dec 26, 2016):

@tboerger we need a colaborative platform to be easy to any Gitea collaborator help and we manage, like Weblate, Pootle and Zanata or Crowdin.

@joubertredrat commented on GitHub (Dec 26, 2016): @tboerger we need a colaborative platform to be easy to any Gitea collaborator help and we manage, like [Weblate](https://weblate.org/), [Pootle](http://pootle.translatehouse.org/) and [Zanata](http://zanata.org) or Crowdin.

GiteaMirror commented

@lunny commented on GitHub (Dec 27, 2016):

I remember @tboerger has sent a request to Weblate?

@lunny commented on GitHub (Dec 27, 2016): I remember @tboerger has sent a request to Weblate?

GiteaMirror commented

@lunny commented on GitHub (Jan 6, 2017):

https://weblate.org/en/hosting/ @tboerger has you apply on this?

@lunny commented on GitHub (Jan 6, 2017): https://weblate.org/en/hosting/ @tboerger has you apply on this?

GiteaMirror commented

@strk commented on GitHub (Jan 6, 2017):

On Thu, Jan 05, 2017 at 07:06:02PM -0800, Lunny Xiao wrote:

https://weblate.org/en/hosting/ @tboerger has you apply on this?

I've made a request but never got an answer.
Never deployed it either so dunno how hard or easy it would be.

@strk commented on GitHub (Jan 6, 2017): On Thu, Jan 05, 2017 at 07:06:02PM -0800, Lunny Xiao wrote: > https://weblate.org/en/hosting/ @tboerger has you apply on this? I've made a request but never got an answer. Never deployed it either so dunno how hard or easy it would be.

GiteaMirror commented

@Bwko commented on GitHub (Jan 8, 2017):

We could host weblate on our own server

@Bwko commented on GitHub (Jan 8, 2017): We could host weblate on our [own server](https://github.com/WeblateOrg/weblate/)

GiteaMirror commented

@joubertredrat commented on GitHub (Jan 8, 2017):

Hi guys,

I can host on my servers too.

--
"O que quer que você faça na vida, será insignificante. Mas é muito
importante que você o faça... por que ninguém mais o fará." Gandhi
"Whatever you do will be insignificant, but it is very important that you
do it... because no one else will it." Gandhi

Joubert "RedRat" - Consultor em tecnologia - Technology consultant
/me at Linkedin http://br.linkedin.com/in/joubertredrat/ and Github
https://github.com/joubertredrat/
~(,,"> RedRat Consultoria

2017-01-08 7:54 GMT-02:00 Bwko notifications@github.com:

We could host weblate on our own server
https://github.com/WeblateOrg/weblate/

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/114#issuecomment-271141093, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABczF5ObntS5fhZ5YsHT_9WELYACXrbXks5rQLJBgaJpZM4KsByg
.

@joubertredrat commented on GitHub (Jan 8, 2017): Hi guys, I can host on my servers too. -- "O que quer que você faça na vida, será insignificante. Mas é muito importante que você o faça... por que ninguém mais o fará." Gandhi "Whatever you do will be insignificant, but it is very important that you do it... because no one else will it." Gandhi ___________________________________________________________________ *Joubert "RedRat"* - Consultor em tecnologia - Technology consultant /me at Linkedin <http://br.linkedin.com/in/joubertredrat/> and Github <https://github.com/joubertredrat/> *~(,,">* RedRat Consultoria 2017-01-08 7:54 GMT-02:00 Bwko <notifications@github.com>: > We could host weblate on our own server > <https://github.com/WeblateOrg/weblate/> > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/go-gitea/gitea/issues/114#issuecomment-271141093>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ABczF5ObntS5fhZ5YsHT_9WELYACXrbXks5rQLJBgaJpZM4KsByg> > . >

GiteaMirror commented

@lunny commented on GitHub (Jan 8, 2017):

If we cannot received the response some days, we could consider host it on our server.

@lunny commented on GitHub (Jan 8, 2017): If we cannot received the response some days, we could consider host it on our server.

GiteaMirror commented

https://github.com/anthonynsimon/parrot

@joubertredrat commented on GitHub (Jan 19, 2017):

This sound suggestive 👍

@joubertredrat commented on GitHub (Jan 19, 2017): This sound suggestive :+1: https://github.com/anthonynsimon/parrot

GiteaMirror commented

@metalmatze commented on GitHub (Jan 19, 2017):

It was already discussed and proposed, so yes. Considering it.

@metalmatze commented on GitHub (Jan 19, 2017): It was already discussed and proposed, so yes. Considering it.

GiteaMirror commented

@lunny commented on GitHub (Feb 5, 2017):

So let's setup parrot and close this issue? @tboerger @bkcsoft any idea?

@lunny commented on GitHub (Feb 5, 2017): So let's setup parrot and close this issue? @tboerger @bkcsoft any idea?

GiteaMirror commented

@tboerger commented on GitHub (Feb 5, 2017):

Parrot doesn't support the ini format, so we most use weblate or something else

@tboerger commented on GitHub (Feb 5, 2017): Parrot doesn't support the ini format, so we most use weblate or something else

GiteaMirror commented

@bkcsoft commented on GitHub (Feb 5, 2017):

@tboerger Are you sure it doesn't?

@bkcsoft commented on GitHub (Feb 5, 2017): @tboerger Are you sure it doesn't?

GiteaMirror commented

@tboerger commented on GitHub (Feb 9, 2017):

@tboerger Are you sure it doesn't?

Yes, I'm sure: https://github.com/anthonynsimon/parrot/tree/master/parrot-api/export

@tboerger commented on GitHub (Feb 9, 2017): > @tboerger Are you sure it doesn't? Yes, I'm sure: https://github.com/anthonynsimon/parrot/tree/master/parrot-api/export

GiteaMirror commented

@lunny commented on GitHub (Feb 10, 2017):

It seems the interface is simple so that we can write an ini one using the same library with Gitea's configuration using.

@lunny commented on GitHub (Feb 10, 2017): It seems the interface is simple so that we can write an ini one using the same library with Gitea's configuration using.

GiteaMirror commented

@tboerger commented on GitHub (Feb 10, 2017):

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.

@tboerger commented on GitHub (Feb 10, 2017): > 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.

GiteaMirror commented

@lunny commented on GitHub (Feb 10, 2017):

And maybe we should move this to v1.2?

@lunny commented on GitHub (Feb 10, 2017): And maybe we should move this to v1.2?

GiteaMirror commented

@tboerger commented on GitHub (Feb 15, 2017):

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

@tboerger commented on GitHub (Feb 15, 2017): 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

GiteaMirror commented

@lunny commented on GitHub (Feb 16, 2017):

Does crowdin has an API?

@lunny commented on GitHub (Feb 16, 2017): Does crowdin has an API?

GiteaMirror commented

@tboerger commented on GitHub (Feb 19, 2017):

Of course it got

@tboerger commented on GitHub (Feb 19, 2017): Of course it got

GiteaMirror commented

@lunny commented on GitHub (Feb 20, 2017):

So how should we copy TRANSLATION back to this repository?

@lunny commented on GitHub (Feb 20, 2017): So how should we copy TRANSLATION back to this repository?

GiteaMirror commented

@bkcsoft commented on GitHub (Feb 21, 2017):

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 😂 )

@bkcsoft commented on GitHub (Feb 21, 2017): 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 😂 )

GiteaMirror commented