RE: translating

You don’t have to translate from Urdu to English because English is already
complete, and Urdu is virtually non-existent.

What you have to do is the reverse: translating from Latin-written English
(which is already complete and maintained by Limewire itself as the source
of all translations) to Arabic-written Urdu.

 

There’s no existing language that is named “English-written Urdu”; Urdu is a
language, English is another language.

 

You are probably mixing languages and scripts; but here also, English and
Urdu are NOT scripts; the scripts are the Latin script (normal script for
writing English) and the Arabic script (normal script for writing Urdu,
although there exists some other transliterations of Urdu using another
script than the Arabic script, for example several non-normalized
romanizations to the Latin script, and transliterations to several Indian
scripts (look at the ISCII Indian standard for such application, but nearly
nobody use something else than the Arabic script, except a few scientific
linguists and scolars).

 

Look at the example Urdu template: it already contains a few Arabic-written
entries for Urdu.

 

Note that Urdu traditionally uses a different calligraphy for the Arabic
script; this is just addressed by a different font, but the encoding is not
altered (the nastaleek “oblique” style is unified and encoded the same way
as the classical “horizontal” style for Arabic) ; so use an editor that is
able to display and edit Arabic correctly, and that supports the
bidirectional editing mode (for example Notepad in Windows): you’ll have
sometimes to play with the leftCtrl+leftShift (and back with
rightCtrl+rightShift) keyboard shortcuts to display the edited file in a
left-to-right (and back into right-to-left) viewing mode.

 

Don’t translate the first keyword before the equal sign (both are appearing
in that order on the left margin in the left-to-right viewing mode, with the
Arabic-written translation on the left, but they will appear on the left
margin when in right-to-left mode when editing the Arabic-written Urdu
translation on the left of the equal sign).

 

Make sure that the Arabic-written Urdu translation appears in the correct
viewing order when reading it in the right-to-left viewing mode (be careful
with final punctuations that may look OK in the L2R mode, but that will be
wrong in the R2L mode), or with some Latin-written words or punctuations
that may be present at the beginning of your translation after the equal
sign (because they will not be reordered…); to make sure that all is ok,
your editing cursor should move from begining to end of the line using the
logical reading order (the non-translatable initial keyword, then the equal
sign, then your translation, then the newline)

 

To make things easier to translate and edit, you may enter a newline after
the equal sign, then enter the Arabic-written Urdu translation on the next
line, then you’ll just merge the two lines by deleting the newline
separator. It should be easier like this to see if the text is correctly
ordered (because the non-translatable initial keyword MUST be encoded and
stored at the logical beginning of the line, independatly of its effective
visual position where the line may eventually logically start on a position
that is not visualized exactly at the margin.)

 

Don’t insert any Bidirectional controls in your translation, unless it is
really needed for inclusions of Latin-written sequences within an
Arabic-written Urdu sentence. Normally, you won’t need such occurrences,
because translations will appear automatically well with the bidirectional
support. Use the normal parentheses if needed (they are mirrored
automatically when viewing the text in right-to-left viewing mode).

 

Yes editing right-to-left languages is not easy (but Arabic writers are now
used to these tweaks when mixing several scripts). But please don’t use
tweaked fonts to edit Arabic in a single visual order, or things will be
non-portable.

 

That’s why I recommend using Notepad or WordPad (note that we don’t use any
text enhancement, we just need pure text, so if you send us a RTF or Word
document, it will be converted back to Unicode-encoded plain text before
use, in a format that tools like Notepad or Vim or Emacs can read, provided
that they have the support for Unicode). We don’t care about which newline
you use (so you can edit the file on a Mac or on Unix/Linux which use
different end-of-lines).

 

You can also use a Windows ANSI Arabic editor (we’ll convert it to Unicode)
if you only have Windows 95/98/ME and don’t have Windows NT/2000 or
XP/Vista.

 

First, start by downloading the current Urdu template from the LimeWire.org
translation status page. Make sure you verify this page to get the latest
version of the files (otherwise, some of your edits may be lost or would
forget important updates, or corrections made by others after your own
submissions).

 

Thanks.

 

Philippe.

 

  _____  

De : [email protected]
[mailto:[email protected]] De la part de sana zeeshan
Envoyé : dimanche 8 avril 2007 09:29
À : [email protected]
Objet : [trans] translating

 

hi. 

i was loking to translate from urdu to english. i just had some queries. if
the question or phrase is written in english,should the translation be
written in roman english urdu? or in actual urdu? if it should be written in
urdu, then how do i get the urdu font?

please reply soon with a helpful reply

regards

sana




  _____  

Txt a lot? Get Messenger FREE on <http://g.msn.com/8HMBENUK/2755??PS=47575>
your mobile. 

----------------------------------------------------------------------------
-----------
Orange vous informe que cet e-mail a été contrôlé par l'anti-virus mail.
Aucun virus connu à ce jour par nos services n'a été détecté.

_______________________________________________
translate mailing list
[email protected]
http://lists.limewire.org/mailman/listinfo/translate