Revision 2663 faq/en/faq_003.xml
| faq_003.xml (revision 2663) | ||
|---|---|---|
| 2 | 2 |
<title>Sylpheed FAQ - Interface</title> |
| 3 | 3 |
<qandaset id="faq-interface"> |
| 4 | 4 |
<?dbhtml cellspacing="13px" ?> <qandaentry> |
| 5 |
<question> |
|
| 5 |
<question id="faq-display-language">
|
|
| 6 | 6 |
<para>How do I make Sylpheed display my language?</para> |
| 7 | 7 |
</question> |
| 8 | 8 |
<answer> |
| 9 | 9 |
<para>You have to set some environment variables, such as |
| 10 | 10 |
<envar>LANG</envar>, <envar>LC_CTYPE</envar>, <envar>LC_MESSAGES</envar> to your local language. |
| 11 | 11 |
Usually <envar>LANG</envar> (or <envar>LC_ALL</envar>) is sufficient. Note that modern distributions and operating systems do this for you automatically.</para> |
| 12 |
<para>Under UNIX, if you need to set e.g. the <envar>LANG</envar> environment variable manually, execute the following command (using <literal>sh</literal> or related shell):</para> |
|
| 13 |
<para><command>export LANG=<replaceable>value</replaceable></command></para> |
|
| 14 |
<para>Replace <replaceable>value</replaceable> with a valid ISO <ulink url="http://en.wikipedia.org/wiki/Language_code">language code</ulink> (e.g. <literal>en_GB</literal> for British English).</para> |
|
| 15 |
<para>If you intend to set the displayed language manually under Windows, you can do so by creating the |
|
| 16 |
<envar>LANG</envar> environment variable with a valid ISO language code value under <menuchoice> |
|
| 17 |
<guimenu>Control Panel</guimenu> |
|
| 18 |
<guimenuitem>System</guimenuitem> |
|
| 19 |
<guisubmenu>Advanced</guisubmenu> |
|
| 20 |
<guibutton>Environment Variables</guibutton> |
|
| 21 |
</menuchoice>.</para> |
|
| 22 |
<para>Also see the <link linkend="faq-environment-variables">question</link> regarding environment variables that have effect on Sylpheed.</para> |
|
| 12 | 23 |
</answer> |
| 13 | 24 |
</qandaentry> |
| 14 | 25 |
<qandaentry> |
| ... | ... | |
| 235 | 246 |
</qandaentry> |
| 236 | 247 |
<qandaentry> |
| 237 | 248 |
<question> |
| 249 |
<para>Execute command for my dynamic signature seems not to be working!</para> |
|
| 250 |
</question> |
|
| 251 |
<answer> |
|
| 252 |
<para>Under Windows, if you have created e.g. a simple batch file to echo a line to be included in your dynamic signature, you need to execute the command (specified under <menuchoice> |
|
| 253 |
<guimenu>Account preferences</guimenu> |
|
| 254 |
<guisubmenu>Compose</guisubmenu> |
|
| 255 |
<guimenuitem>Signature</guimenuitem> |
|
| 256 |
<guilabel>Command output</guilabel> |
|
| 257 |
</menuchoice>) using either forward slashes or double |
|
| 258 |
backslashes for paths, for example:</para> |
|
| 259 |
<para><command>cmd /c 'c:\\signature.bat'</command></para> |
|
| 260 |
<para>Note that it is also recommended to enclose paths with single quotes, as is illustrated above.</para> |
|
| 261 |
</answer> |
|
| 262 |
</qandaentry> |
|
| 263 |
<qandaentry> |
|
| 264 |
<question> |
|
| 238 | 265 |
<para>Where is the Bcc when I compose a mail?</para> |
| 239 | 266 |
</question> |
| 240 | 267 |
<answer> |
| ... | ... | |
| 279 | 306 |
</answer> |
| 280 | 307 |
</qandaentry> |
| 281 | 308 |
</qandaset> |
| 282 |
</chapter> |
|
| 309 |
</chapter> |
|
Also available in: Unified diff