Farsi - #375
Merged
Merged
Conversation
appleboy
suggested changes
Feb 8, 2017
appleboy
left a comment
Member
There was a problem hiding this comment.
Your format is different from origin README. Can you describe why change the format?
Contributor
Author
|
As you may know, Farsi (like Arabic or Hebrew) is Right-to-Left. however, once you combine it with some English (or codes) it will mess everything up, including order of contents. I hope it could demonstrate the reason why Farsi's format is different. |
|
Why Farsi directory not exist in Translation folder? |
appleboy
approved these changes
Mar 24, 2017
Contributor
|
@ghaseminya because no one had translated it to Farsi before this PR. |
|
@strugee yes, its merged, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've add Farsi (Persian) translation of the document.
I'm really sorry about not following the rule of 'Just one Commit' thing ... but creating a bidirectional markdown proved to be a pain in the butt!