Character encoding

Some packages have to be included in the preamble to support it, as shown below.

\documentclass[a4paper,10pt]{article}
%In the preamble section include the arabtex and utf8 packages
\usepackage{arabtex}
\usepackage{utf8}

\begin{document}
%start encoding to unicode
%Note that your layout must support arabic text when compiling
\setcode{utf8}
%To start typing in Arabic use the command arabtext
hello
\begin{arabtext}
السَلامُ عَليكم ورَحمةُ الله وبَركاته
\end{arabtext}
arabic
\end{document}

Some packages have to be included in the preamble to support it, and it should be written as shown below:

\documentclass[a4paper,10pt]{article}
%In the preamble section include the arabtex and utf8 packages
\usepackage{arabtex}
\usepackage{utf8}

\begin{document}
%start encoding to unicode
%Note that your layout must support arabic text when compiling
\setcode{utf8}
%To start typing in Arabic use the command arabtext
hello
\<السَلامُ عَليكم ورَحمةُ الله وبَركاته >
arabic
\end{document}

I will explain a solution for the popular Open-Source tool Filezilla. Other FTP tools might handle charset encoding differently.

FileZilla offers three different charset settings:

  1. Autodetect
  2. Force UTF-8
  3. Use custom charset

Per default, FileZilla tries to detect the correct charset on its own. If this doesn’t work and your server uses some custom charset encoding, you need to set it via the Site Manager. In the tab “Charset”, a custom charset encoding can be specified for each individual server. Once it’s set, the specified charset encoding will be used for all future connections to this server and the filenames will be correct.

Subscribe to Character encoding