Website Translation

[abdelgmartinezl]

Hello! I would like to translate the site to Spanish.

I see there's no project on Zanata... Where do I start translating?

Thank you in advance!

[phracek]

Based on mail from Jean-Baptiste, I would prefer to start a project on Zanata. https://lists.fedoraproject.org/archives/list/developer-portal@lists.fedoraproject.org/message/BXCA7UVJKHQC4DY3SHZEIQBOXCL3GGLQ/

[anamativi]

I would like to help with Portuguese (Brasil) translations. I'm following the discussions on the mail list as well.

[Jibec]

Thanks @phracek for your help. As we are on wishlist, I share you the link about a recent discussion with Ralph Bean from infra team. I think the same advice applies here. #https://github.com/fedora-infra/asknot-ng/issues/69 Let us know when we can start translating :)

[1dot75cm]

Very nice. I would like to help with Chinese translations.

[phracek]

Add reference to infra ticket https://fedorahosted.org/fedora-infrastructure/ticket/5265

[phracek]

@Jibec You can start with translating. But my question is. What shall we do from Fedora Developer Portal team? Shall I create zanata.xml file and I10n directory with all files like is mentioned on asknot-ng?

Portal is about huge texts and not like messages? Shall we prepare a references for texts like is mentioned here https://github.com/fedora-infra/asknot-ng/blob/develop/l10n/fedora/locale/af.po#L24

[strzibny]

This is great to see people wanting to do the translations, but before we should probably decide how this is going to work. It could happen that translated content will not keep up with the original and become obsolete. Also, technically, we have nothing in place to support translations.

[Jibec]

@phracek : you should produce your project in Zanata and add the necessary mechanism to produce po files and publish translated content in developper-portal. Easy to write, probably less to do.

At the moment, simply translate ".md" files won't be sufficient. Text has to be smaller (as much for translation memory as for ease to manipulate) and to be in context (cf infra ticket : cut po files according to subjects).

I agree with @strzibny, you need first to know how to produce a translated website and how to handle process, but this answer has to be produce by developers. We said month ago we were interested. Websites and docs team already have experiences in the subjects. Translators translate only if developers accept to handle it. There is no argument about obsolescence of content as each time the strings change, it won't be translated and will be in English (one more reason to translate small messages). It will look ugly, but it's the translator job to keep the rhythm, and the producer job to group changes and limit endless modification. Yes, you need a formal or informal process.

Fedora needs to reach more users, we believe translation is one way to go. But we can't do it without you. Thanks again for you help, I'm sure it will succeed !

[alex-sl-eng]

Given all the content is in .md format, we might need to upload to Zanata as File project type and use text filter to parse it. The project maintainer need to prepare these before translators can start working on the translations.

Let me know if you need any help on that. http://docs.zanata.org/en/release/user-guide/documents/upload-documents/

[Jibec]

hi @phracek, any updates or tests so far ? Thanks for your help

[phracek]

@Jibec I did not start it yet:( Sorry I was a pretty busy with another stuff. But as @aeng mentioned upload-documents would be a right way.

[phracek]

@aeng I have created a project on Zanata for Fedora Developer Portal. https://translate.zanata.org/project/view/developer-portal?dswid=-454

Soon I will send documents which needs to be translated. Question is to define a way how to distribute translations. We don't want to include translation into our GitHub repo. Where the translations will be stored?

[Jibec]

hi there, long time no see, any news here ? You should contact Website team, they do not commit translation in git and it works fine (I do not understand the choice, but as far as it works...). Thanks for your help, (btw, I feel like Pagure have everything you need from live edits to documentation hosting, git and issue tracker)

[alex-sl-eng]

@phracek What framework the website is operating in? If it support internationalisation, then it should have someway to store the translation files.

[strzibny]

@aeng it's built on Jekyll.

[jackorp]

There is a question on how to implement this. A lang attribute can be added in the yaml headers of the markdown files to help define what language the content is. I found a post for inspiration: https://sylvaindurand.org/making-jekyll-multilingual/.

[pvalena]

Best-effort, and quick (but I think it really works great) solution would be to put this link somewhere:

https://translate.google.com/translate?hl=en&sl=en&tl=en&u=https%3A%2F%2Fdeveloper.fedoraproject.org%2F

And, maybe (if it's not apparent), instruct users to select their language from the second select menu.

[strzibny]

@pvalena I like the idea. Mostly because maintaining full translations for this site would be extremely difficult, and they would quickly go EOL. I think translations make sense when things almost "done."