Please transfer openttd-android-translate repo to the new translator

[pelya]

The old Android translations git repo is at
ssh://hg@hg.openttdcoop.org/~/openttd-android-translate
It contains translations for touch-specific options like title bars and button size.
Could you please transfer this repo to the new translator?

[TrueBrain]

Just as an update: we are not ignoring you or anything, just talking over if/how we should do this :D

To be clear, openttdcoop.org used to host a SaaS variant of eints, where everyone could create their own project. One of them is yours.
OpenTTD never supplied eints as a SaaS; it hosts only our own projects (those in the https://github.com/OpenTTD namespace). It is also tightly coupled with our own infrastructure.
So there is no simple "transfer" as such; we have to recreate the SaaS, mostly meaning it has to become less coupled to our own infrastructure.

For example, one of those tightly coupled things: @DorpsGek needs push rights in the default branch of the GitHub repository for the project being translated (it cannot make Pull Requests currently). This might not be ideal for other projects, like yours.

So, we are looking into if and how we can offer eints as a SaaS via openttd.org. This will take some time to figure out.

[pelya]

So should I just use a service like https://gitlocalize.com/ or https://poeditor.com/ ? They support a bunch of formats like .po and .json, but of course OpenTTD localization uses a different format. Do you have some tools to convert between .po and OpenTTD .txt localizations?

…

On Mon, 24 May 2021, 16:42 Patric Stout, ***@***.***> wrote: Just as an update: we are not ignoring you or anything, just talking over if/how we should do this :D To be clear, openttdcoop.org used to host a SaaS variant of eints, where everyone could create their own project. One of them is yours. OpenTTD never supplied eints as a SaaS; it hosts only our own projects (those in the https://github.com/OpenTTD namespace). It is also tightly coupled with our own infrastructure. So there is no simple "transfer" as such; we have to recreate the SaaS, mostly meaning it has to become less coupled to our own infrastructure. For example, one of those tightly coupled things: @DorpsGek <https://github.com/DorpsGek> needs push rights in the default branch of the GitHub repository for the project being translated (it cannot make Pull Requests currently). This might not be ideal for other projects, like yours. So, we are looking into if and how we can offer eints as a SaaS via openttd.org. This will take some more to figure out. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABF5QA7CGJKBZG6YOXB2PLTPJJSPANCNFSM44SPNMVA> .

[TrueBrain]

So should I just use a service like https://gitlocalize.com/ or https://poeditor.com/ ?

That fully depends on you, of course. But that is not what I said. I am saying it is not a simple "transfer" as such, and we need some time to see how we want to create a SaaS out of our eints deployment. This won't be done overnight. My message was purely to inform you we have seen your request, and are looking into it.

[pelya]

Okay, thanks. I'll wait for some news from you then.

…

On Mon, 24 May 2021, 23:58 Patric Stout, ***@***.***> wrote: So should I just use a service like https://gitlocalize.com/ or https://poeditor.com/ ? That fully depends on you, of course. But that is not what I said. I am saying it is not a simple "transfer" as such, and we need some time to see how we want to create a SaaS out of our eints deployment. This won't be done overnight. My message was purely to inform you we have seen your request, and are looking into it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABF5QC3ESFEG4SLRXQYDLDTPK4YRANCNFSM44SPNMVA> .