Repository:

https://github.com/iFixit/iFixitAndroid

---

Let's repeat the basics:

You can skip the long version and go to the TL;DR below

Project Details:

• The official site describes iFixit as:

iFixit is a wiki-based site that teaches people how to fix almost anything. Anyone can create a repair manual for a device, and anyone can also edit the existing set of manuals to improve them. Our site empowers individuals to share their technical knowledge with the rest of the world.

So what are you waiting for?

(source: https://www.ifixit.com/Info)

Basically, it is a wiki of DIY tutorials. You can learn how to fix almost anything, from your broken games console to your smartphone or tablet and many many more! Users from all around the world have access to this information and can help out make the site better, by submitting their guides or enhancing the already saved guides.

• The original language of the text is English, which as a teacher and a long-term speaker, I know very well. The volume of the text is quite large, with 48,669 words to translate. Regarding the difficulty of the language used, the text is of average difficulty, with some developer's terminology to take into account.

• @dimitrisp is in charge of the proofreading and corrections suggestions. Being a developer and a fluent speaker of both Greek (his mother tongue) and English, he has all the qualifications for the task. (His crowdin profile can be found here: https://crowdin.com/profile/dimitrisp2)

---

Why I chose this project out of many others?

I was unaware of this site's existence until I started working with Davinci and Utopian. iFixit was on the whitelisted projects, so as a Language Manager of the Greek team, I had to check it out. Once Language Managers were allowed to submit translations themselves, I picked this out of the "bucket".

The reasons are three:

1) The value it brings: iFixit offers invaluable help and guidance to people around the world who turn to DIY solutions instead of hiring a professional. (You can also order the necessary parts and tools from their e-shop.)

2) The difficulty level: It seemed to be a manageable project, compared to a wide variety of more difficult projects that revolve around programming and web developing jargon.

3) Personal reasons: Having a carpenter father, with knowledge on how to fix lots of things around the house (from the leaking tap to a broken hairdryer), I felt a distant connection to this project.

---

Contribution Specifications

Translation Overview:

When I began translating on Crowdin, several parts of the project had already been translated by other contributors outside the Davinci-Utopian collaboration. This meant I'd have to go through all their suggested translations and check their accuracy and correct use of the Greek language. Some were appropriate, others needed minor corrections (a few missed strains, spaces and misspellings), while others needed to be totally re-written as they were wrong.

Languages:

The original text is all written in English and my task is to translate it into Greek, which is my mother tongue and I have great knowledge of. Being a teacher, it is my job to speak and teach my language correctly.

Activity Overview

In this part I finished the second file API.po. This part contained some dev terminology, but thanks to our very helpful LM, @dimitrisp, I managed to clarify those terms and learn new things in the process.

Do you want an example?

Endpoint: An endpoint is a site built to return results from a database on a specific server.

Word Count:

As I said, the project has 48,669 words. In this session I finished the second file, API.po. According the Crowdin word count tool, the volume of the English text I went through was 1,428 and I delivered a translation of 1,261 Greek words.

This part did not have as many code strings as the first one, so I'll have to deduct a 5-7% for:
a) words that we chose to keep in English (like email and repository), since they are broadly used in our everyday language,
b) variables and code strings that need to remain untouched,
and
c) duplicate strings (in this case I think it was only one).

This leaves us with about 1,170 words.

Note: The previous contribution was about 1,300 words.)

Proof of Authorship:

• My Crowdin Profile: https://crowdin.com/profile/ruth-girl

• My GitHub Profile: https://github.com/ruthinoute

• iFixit on Crowdin: https://crowdin.com/project/ifixit

Note: No Activity Screenshots were added after a specific new guideline we received on August 2nd, 2018.

---

TL;DR

I am translating iFixit from English to Greek. It's a website where you can find various helpful guides and tutorials on how to fix your electronics and not just that. It is a long text of almost 48,500 words. I have finished the first two files, the second file had some tricky dev terms, but I managed with the help of the developer LM @dimitrisp. In this session I translated about 1,170 words, the previous contribution was 1,300 words long. I can now move on to the next files, which do not seem as demanding in terms of jargon.

---

Credits:

Again, a big thank you goes to our new Greek Language Manager, @dimitrisp, he always explains why some things must be translated in a certain way, because the meaning would be different or wrong if done in a different way.

And a shout-out to the rest of the Greek team:
@katerinaramm, @lordneroo and @trumpman, keep it up guys! You are all doing great!

---

Thank you for taking the time to read this!

And another big thank you goes to Davinci and Utopian for supporting this venture!

---

PS:

Do you have any questions, suggestions or anything else that you'd like to see in these contributions of mine? I am all ears to see what you might want!