اردو ٹرانسلیشن گائیڈ

ورڈپریس اردو ترجمے کی بڑھتی ہوئی ٹیم کو دیکھتے ہوئے فوری طور پر ایک گائیڈ پبلش کی جارہی ہے، جس کا مقصد ہے نئے آنے والے مترجم کو ترجمے کا عمل سمجھانا اور یہ بتاناکہ کس طرح سے ترجمے اور اس کی ٹیم کا سلسلہ چلتا ہے۔  اس مقصد کے لیے اس سائٹ پر چند پوسٹس کی گئی ہیں اور ان کے لنک اس گائیڈ میں موجود ہیں۔ وقتی طور پر یہ گائیڈ انگلش میں ہیں اور ورڈپریس فاؤنڈیشن کی طرف سے جاری کردہ ہیں، وقت کے ساتھ ساتھ ان کو اردو میں منتقل کر دیا جائے گا۔

  1. اردو ترجمہ کرنے کی ابتدائی گائیڈ
  2. اردو ترجمے کےچند اصول
  3. پروجیکٹ ایڈیٹر کی درخوست کا عمل
  4. عمومی ایڈیٹر بننے کی درخواست کا عمل

تمام مترجم سے درخواست ہے کہ ان اصولوں پر عمل کریں، تاکہ ہم ساتھ مل کر آگے بڑھ سکیں۔

On Boarding Process for GTEs

After serving the locale as a PTE, next step forward is to become a GTE for your locale. Below are some rules devised to entertain the GTE requests.

To be a GTE:

  • You’ve to be a PTE of at least 2 projects, for a month at least, with 100% translations. Self-authored plugins/themes excluded.
  • Organize at least one translation meetup and guide the attendees how to translate. Quality of the translation being done by the attendees under our guidance really matters.

Also, you have to understand the fact that GTE is a higher level of commitment. You’re the one going to lead, guide, and onboard new translators. So make sure you’ve got enough time and energy to spend in this open source project.

  • Also: We’ve got some technical expectations on a GTE:
    • Show a real name and a real photo in your profile
    • Make sure that you add #ur tag as a followed string in: https://profiles.wordpress.org/me/profile/notifications/ 
  • Participate actively in the local translation team.
  • Feel free to step down if time and energy doesn’t suffice. Nobody can be a superhero all the time.

Once you successfully qualify the criteria, put forward a request and current GTEs team will respond to that.

On Boarding Process for PTEs

Following the path of some other locales, here are the guidelines for all WordPress Translators who wish to have their favorite products (themes, plugins) localized in Urdu, to give it a wider chance to be adopted by Urdu users.

In order to assure the best possible quality for all translations (and therefore for the products you so dearly worked on to translate), we have established a few rules to grant you PTE (Project Translator Editor) status for the project(s) that interest you:

  1. We will accept your request only if you write and speak Urdu fluently.
  2. We expect you to follow these steps:
    • Join the Urdu Slack community.
    • Translate as a Contributor (Any person logged in at WordPress.org can contribute suggested translations. If you make an error, you may reject your own translation and submit a new one.)
    • Inform the translation team about your translation and ask them to review your contribution.
    • A PTE or a GTE (General Translator Editor) will review your translations and give you the feedback;
    • If the quality of your translation is up to the standards the communities try to follow, you will be granted PTE permissions.
    • Now that you have been granted PTE permissions, you can approve, reject or edit translations. You can also mark translations as “fuzzy”.

WHY WE FOLLOW THESE GUIDELINES

  • We strive for excellence: We aim to create the best possible localization for all products in the WordPress ecosystem. Since localization can determine a product’s user experience in a given language, all translations should be done in the best possible way.
  • It helps us create a community of translators for our locale that knows each other and can support each other when needed.
  • We think globally.
  • We aim at consistency.
  • It streamlines and optimizes the process, reducing the amount of “improper” translations and the time spent on rejecting and revising translations (thus allowing more time to be devoted to the actual localizing)

These rules are meant to give you the best possible localization for your product(s) and to contribute to enhanced user experience, a stronger platform, and a healthier ecosystem to work on for the whole WordPress community.

Good luck with translation.

Useful links:

Check Urdu glossary

Getting Started With Urdu Translation of WordPress

You can start suggesting translations by following these simple steps:

  1. Log in to WordPress.org or create a new account
  2. Go to WordPress Urdu Translation Page
  3. Click “Contribute Translation”
  4. Select the type of project (WordPress core, Themes, Plugins, Meta, or Apps)
  5. Click the “Translate Project” button for one of the listed items
    Screenshots 09/06/2015 20:01:47
  6. Click one of the items under “Set / Sub Project”
  7. Click the “Details” link on the string to translate (you can also click a row)Screenshots 09/06/2015 19:55:32
  8. Enter your translation, then click “Suggest new translation

Great! You made your first contribution to WordPress!

A couple of additional hints:

Expectations

As a translator, you want to make sure the language of the localized project is well-polished. Establishing and following translation rules might seem like a lot of extra work if you are just starting out. But in fact, it helps cut the translation team’s workload by reducing the need for correction and clarification.

 

  • Don’t include random links:

 

The language files for WordPress projects should only contain links to pages found in wordpress.org domains (or other relevant project domains such as bbpress.org) or the translation community’s official documentation. If you need to link to a translated version of the original link, make sure it has a permanent home in one of those places. Including commercial links in translations can lead to a removal from the translation team.

 

  • Don’t translate literally, translate organically:

 

As a translator, you undoubtedly know that each language is unique. Given that, try to avoid composing your translation in the same structure as the original English string, while sounding natural and still conveys the same message.

 

  • Try to keep the same level of formality (or informality):

 

WordPress messages (informational messages in particular) tend to have a politely informal tone in English. Try to accomplish the equivalent in the target language, within your cultural context.

 

  • Don’t use slang or audience-specific terms:

 

Refrain from using colloquialisms that only a certain group of readers will understand. If the uninitiated blogger were to install WordPress in Urdu, would they know what the term means? Words like pingback, trackback, and feed are exceptions to this rule; they’re terminology that are typically difficult to translate, and many translators choose to leave in English.

 

  • Learn from other localizations in your language:

 

To get a feel for things like commonly used terms and formality level, try reading through the translations of other popular software or service. Of course, WordPress has its own tone and feel, so keep that in mind when you’re reading other localizations, but feel free to dig up UI terms and the like to maintain consistency with other software in your language.

 

  • Keep it consistent:

 

Consistency is one of the most important characteristics of high quality translation. To maintain consistency throughout various WordPress projects, you can use glossary of Urdu.

The section below needs to be incorporated with the one above:

Don’t translate literally, translate organically

Being bi- or multi-lingual, you undoubtedly know that the languages you speak have different structures, rhythms, tones, and inflections. Translated messages don’t need to be structured the same way as the English ones: take the ideas that are presented and come up with a message that expresses the same thing in a natural way for the target language. It’s the difference between creating an equal message and an equivalent message: don’t replicate, replace. Even with more structural items in messages, you have creative license to adapt and change if you feel it will be more logical for, or better adapted to, your target audience.

Try to keep the same level of formality (or informality)

Each message has a different level of formality or informality. Exactly what level of formality or informality to use for each message in your target language is something you’ll have to figure out on your own (or with your team), but WordPress messages (informational messages in particular) tend to have a politely informal tone in English. Try to accomplish the equivalent in the target language, within your cultural context.

Don’t use slang or audience-specific terms

Some amount of terminology is to be expected in a blog, but refrain from using colloquialisms that only the “in” crowd will get. If the uninitiated blogger were to install WordPress in your language, would they know what the term means? Words like pingback, trackback, and feed are exceptions to this rule; they’re terminology that are typically difficult to translate, and many translators choose to leave in English.

Read other software’s localizations in your language

If you get stuck or need direction, try reading through the translations of other popular software tools to get a feel for what terms are commonly used, how formality is addressed, etc. Of course, WordPress has its own tone and feel, so keep that in mind when you’re reading other localizations, but feel free to dig up UI terms and the like to maintain consistency with other software in your language.

اردو سے محبت کرنے والوں کو میرا سلام۔

مجھے یہ بتاتے ہوئے بہت خوشی محسوس ہو رہی ہے کہ اردو ٹیم کی بھرپور محنت اور لگن کی وجہ سے ہم نے ورڈپریس کے تازہ ترین ورژن 4.9 کا اردو ترجمہ مکمل کر لیا ہے اور اب یہ ڈاؤن لوڈ کے لیے بھی دستیاب ہے۔

اردو میں ٹیم کی 02…

اردو میں ٹیم کی 02 سائٹ منظر عام پر آ چکی ہے کسی پراجیکٹ پر تبادلہ خیال یا ترجمے کے دوران کسی میں پریشانی کی صورت میں یہاں اردو ترجمہ ٹیم سے رابطہ کیا جا سکتا ہے۔ اردو مترجموں سے التماس ہے کہ یہاں بات چیت میں اردو زبان کو فوقیت دیں۔ شکریہ

کاپی: @mrahmadawais @amreendanish @hibashaikhpk @mbilalkhan90 @saqibameen @sajidzaman

ٹیم کے O2 پر خوش آمدید

ہم ہر لوکیل ٹیم کو ان کا اپنا بلاگ دینے پر خوش ہیں، جو WordPress.org پر، آپ کے رابطے کو آسان بنانے کی اجازت دیتا ہے۔ آپ اس سائٹ کو مرضی کے مطابق بنا سکتے ہیں اور ضرورت کے مطابق، صفحات شامل کر سکتے ہیں۔ اگر آپ کے سوالات ہیں تو، ہماری میٹا ٹیم کو بتائیں۔

O2 کا استعمال کیسے کریں

O2 ایک تھیم اور ایک پلگ ان کا مجموعہ ہے جو کہ آسان اشتراک کی اجازت دیتا ہے۔ یہاں چند خصوصیات ہیں جو آپ کی ٹیم کی سرگرمیوں میں ہم آہنگی پیدا کرنے میں مددگار ثابت ہونگی:

1۔ @تذکرے: آپ کسی کے اسم رکنیت کے آگے @ لگا کر WordPress.org نیٹ ورک پر ان کا بھی تذکرہ کر سکتے ہیں۔ آپ کی لوکیل سائٹس (بشمول آپ کی مرکزی سائٹ، آپ کا فورم، اور O2) کے ارکین خود کار طریقے سے آٹو کمپلیٹ سے شامل ہو جاتے ہیں۔

ٹیگز: ٹیگنگ سے پوسٹوں اور تبصرے کے اندر آسانی سے شامل کیا جا سکتا ہے۔ مثال کے طور پر، #welcome ٹیگز کے ساتھ یہ پوسٹ ” welcome”۔ ایک ٹیگ پر کلک کریں اور تمام ٹیگ کردہ پوسٹیں دیکھیں۔

کراس پوسٹیں: + کی علامت کا استعمال کر کے WordPress.org کی دیگر O2 سائٹ پر کراس پوسٹ کریں۔ آپ O2 استعمال کرنے والی کسی بھی سائٹ پر کراس پوسٹ کر سکتے ہیں۔


یہی ہے! اپنے نئے بلاگ کا لطف اٹھائیں اور آپ کو کسی بھی مسائل کا سامنا ہو تو میٹا ٹکٹس دائر کریں۔