Translation to pt_BR. about beeware.github.io HOT 20 CLOSED

ok, @freakboy3742 - working on pages project folder.
PR coming soon.

from beeware.github.io.

@goanpeca FWIW - we already have a bot account with repo modification permissions (@brutusthebee) - if we need another one specifically for translations, that's no problem either.

I'll have a read and poke around crowdin and see what is involved.

from beeware.github.io.

I'm translating the homepage.

I'm also working on the links and navbar and fixing things site-wide to improve our translation effords.

from beeware.github.io.

hello.what is status on this? I can jump in too.

from beeware.github.io.

@joncasdam Any page on the BeeWare site that doesn't have a +pt_BR version still requires translation. You can also review any of the existing pages to confirm the translation is accurate.

from beeware.github.io.

Hi, everyone!

It seems that nobody has been working on the Portuguese translations for quite some time. I'll try to do a bit each day, when I find some free time.

BTW, there are plenty of "Crowdsourced Translations Managers" that are free for OSS, such as POEditor, Transifex, OneSky, Crowdin, Zanata, Launchpad, and more. They are usually pretty good to manage both software and website translations, with their own revision features (some down even to single strings). IMHO, they are much better than GitHub to work with multiple languages translations...

from beeware.github.io.

@AltoRetrato Thanks for the suggestion - I'm definitely in favour of anything that will make translator's lives easier.

I've worked with Transifex before - however, I haven't had any luck getting in contact with their team to set up a FOSS account. Do you have any suggestions/preferences amongst those tools?

from beeware.github.io.

I had some discussion of options and how django girls tutorial is setup wth crowdin (https://crowdin.com/)

DjangoGirls/tutorial#1271

It would require setting up a "bot account" and some additional scripts, but could help in the translation process.

from beeware.github.io.

I think crowdin gives foss to accounts not orgs and that is why we need a bot so the bot has a fork of the website and is linked to that repo.

from beeware.github.io.

@freakboy3742 From the group I've listed, Crowdin was my favorite: very fast, easy to use and with great features, and a real joy to use. It supports many import / export formats, and have a nice API.

As you might have already seen, the Open Source project setup request form must be filled / submitted by the project lead.

from beeware.github.io.

It is worth noting that we will be still useing .lr files, which is not the same as plain .rst or .md for which those platforms might be better suited.

from beeware.github.io.

Crowdin currently supports 30+ formats, and unsupported formats are treated as plain text files. It seems that .lr files could be used as-is (i.e., as .txt), or if someone is inclined to, a script could be written to automatically convert to/from a supported format during import/export.

from beeware.github.io.

@AltoRetrato yes, what I am saying is that the lektor format is more susceptible to corruption if the user accidentally changes a key or removes a -- in a section separating contents,

from beeware.github.io.

True - but that also goes for the current state of the translations, right?

Another option would be to use a different format and convert to/from it, but I don't know the Lektor file structure/requirements, so I have no idea if a simple conversion to/from, e.g., JSON, would suffice.

from beeware.github.io.

True - but that also goes for the current state of the translations, right?

No, cause they are PRs that can be reviewed, and run tests.

Another option would be to use a different format and convert to/from it, but I don't know the Lektor file structure/requirements, so I have no idea if a simple conversion to/from, e.g., JSON, would suffice.

I don't think this is worth it

from beeware.github.io.

However there is a lektor feature in progress that would allow embedding files as the content of a field, so for long content, we can have a separate file that is purely md or purely rst. But that would probably be an unnecessary complication as more languages appear

from beeware.github.io.

True - but that also goes for the current state of the translations, right?

No, cause they are PRs that can be reviewed, and run tests.

The same process could be applied via Crowdin, too: after a batch of translations are done, a script would be invoked to download the .lr files from Crowdin, run automatic tests and make a pull request for each one that pass.

from beeware.github.io.

Closing due to a lack of activity. If anyone is interested in submitting a Brazilian (or any other translation), we don't need a ticket; submitting only the PR for the translation update is fine.

from beeware.github.io.

Closing due to a lack of activity. If anyone is interested in submitting a Brazilian (or any other translation), we don't need a ticket; submitting only the PR for the translation update is fine.

IIRC, I sent a few PRs that required local testing with Lektor (and screenshots to prove it), so they were never approved...

from beeware.github.io.

@AltoRetrato Apologies for that - we definitely don't want the efforts of contributors to be wasted.

I've recorded #393 as a possible fix that will (hopefully) prevent others having the same experience.

from beeware.github.io.