Re: translation for Persian (FA)

"Philippe Verdy" <[email protected]> Sat, 20 Jan 2007 21:30:10 +0100
Newsgroups gmane.network.gnutella.limewire.translate
Organization Ordinateur Personnel
Message-ID <0bab01c73cd1$c85ba870$0a01a8c0@HARNON>
Can you confirm that your attached HTML document was encoded using the Windows Arabic character set?

Your email was just labelled with the "text/html" format and no explicit charset. Such format is often not correctly handled when sending emails, because many agents assume this may be ASCII or ISO 8859-1 and may filter out some codes, or introduce extra line breaks in the text (even if it's HTML) which may break the translations.

Note: your translation was first checked through our validator to check for missing or incorrect lines. It looks OK when I decode your translation with the Windows Arabic character set (except that there were just missing empty lines which are restored here).

Note however that its current translation level (14.44% translated) is still not enough for a publication. There are more work needed to get the minimum required for being published in the LimeWire distribution.

The file in attachment is encoded with UTF-8 (a standard 8-bit character encoding of Unicode, internationally supported in almost all environments, preferable to the native Windows encodings), from your translation (as is this email because I have manually selected the UTF-8 encoding before sending, which forces the email to be sent in "Quoted-Printable" format to preserve line-lengths, the representation of linebreaks, will preserves spaces, and the complete character encodings, without depending on 8-bit support during email transfers, something that is not reliable):

Do the same explicit encoding selection when you are attaching text files in emails, using the options in your email agent, or first zip the attached file if you can't do that, for example when you use an online webmail form. If you zip your text, the ZIP file attachment will be sent in the reliable "Base-64" format, which is also reliable for binary file attachments without depending on binary 8-bit support during its transport.

I suggest that you send your translations in an separate text file attachment rather then in the email body, preferably zipped to avoid all possible alteration by email transfer agents or SMTP relays, if your email can't specify the charset explicitly, or that you set your email agent to use a QuotedPrintable format when composing the email body with HTML containing Arabic characters.

Thanks.

_______________________________________________
translate mailing list
[email protected]
http://lists.limewire.org/mailman/listinfo/translate
MessagesBundle_fa.UTF-8.txt (text/plain, 231.2 KB) - not displayed