Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kitsunenosara t chapters #16

Merged
merged 7 commits into from
Apr 11, 2017
Merged

Kitsunenosara t chapters #16

merged 7 commits into from
Apr 11, 2017

Conversation

kitsunenosaraT
Copy link
Member

Create new folder whit separate files for each chapter of the guide.
See each file for a description of the relative chapter.

This is the introductory chapter of the Mozilla Italia l10n Guide. It deals with such matters as what Mozilla Italia is, the meaning of localization in our Vision, the life of a volunteer translator etc.
This is the first chapter of the guide and deals with such matters as general translation best practices: syntax, punctuation, false friends etc.
This is the second chapter of the guide and deals with such matters as Mozilla Italia's guidelines: translation criteria for new/technical terms ("to translate or not to translate" dilemma), adapting style to different contents etc.
This is the third chapter of the guide and deals with such matters as the translation workflow: how to work together with your reviewer in Pontoon, Sumo, MDN etc.
This is the fourth chapter of the guide and deals with such matters as dealing with different file types: HTML tags, .lang, .po, text editors and CAT tools recommendations
This is the fifth chapter of the guide and deals with such matters as external resources: open glossaries, free online dictionaries etc.
@kitsunenosaraT kitsunenosaraT merged commit 11c6c23 into master Apr 11, 2017
@kitsunenosaraT
Copy link
Member Author

The Chapters folder contains one dedicated file for each chapter of the guide. See each file for the chapter descriptiom

@kitsunenosaraT kitsunenosaraT deleted the kitsunenosaraT-chapters branch April 11, 2017 13:23
@gialloporpora
Copy link
Collaborator

gialloporpora commented Apr 12, 2017 via email

@kitsunenosaraT
Copy link
Member Author

Thank you for anticipating me 😁
I think the more pressing ones are chapter 3 and 4.
You wrote the majority of the source material about file types and are more knowledgeable than me on the topic, while I've been going through the workflow many times recently with eliogi… How about you take chapter 4 and I chapter 3?

But before that, I would like to give priority to the Code of Conduct (for you) and the Contributing (for me) files, since in today's Call I was said that we need them as soon as possible in order to register the project to the Global Sprint.

@gialloporpora
Copy link
Collaborator

gialloporpora commented Apr 12, 2017 via email

@eliogi
Copy link
Collaborator

eliogi commented Apr 13, 2017

Hi everybody,
please, tell me how I could support you.
I've already finished my answers to the survey.

@kitsunenosaraT
Copy link
Member Author

@eliogi Wow, thank you for going through the survey!
Can you please copy your answer in the comment section of Issue #7 I think it will be easier for new contributors to write after reading your example.

About the guide, please don't feel left out if I didn't assign you any chapter yet.
At this stage (first draft) we need more than ever an external point of view to point out the shortcomings in our method, if it does make sense.
As the most recent team member and junior translator you are in a unique position to review the first draft and detect the weakest parts, so I need you to keep your distance so that you will see the guide with a fresh mind.

Of course things will change radically with the second draft: you will be able actively involved in the rewriting of the final guide and will also be encourage to add parts of your own.
So, please, have still a little patience 😉

@eliogi
Copy link
Collaborator

eliogi commented Apr 14, 2017

@kitsunenosaraT hi Sara, I've done the task you suggested me. I've copied my comment at the end of the thread of issue #7 .
Don't worry for me it's ok. I didn't know exactly how to proceed; so now it's all clear and I agree with the methodology adopted by you.
So... let's good.
I'm available for cooperation when you need me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants