-2.1.8 (16 May 2007)
+2.1.10 (18 May 2007)
-2.1.8 (16 May 2007)
+2.1.10 (18 May 2007)
foreign characters the {bf LANG} environment variable
must end in {\bf .UTF-8}. An full example is {\bf en\_US.UTF-8}. The
exact syntax may vary a bit from OS to OS, and exactly how you define
-it will also vary.
+it will also vary. On most newer Win32 machines, you can use {\bf notepad}
+to edit the conf files, then choose output encoding UTF-8.
Bacula assumes that all filenames are in UTF-8 format on Linux and
Unix machines. On Win32 they are in Unicode (UTF-16), and will
must end in {\bf .UTF-8}. An full example is {\bf en\_US.UTF-8}. The
exact syntax may vary a bit from OS to OS, and exactly how you define it
will also vary.
+
+ On most modern Win32 machines, you can edit the conf files with {\bf
+ notebook} and choose output encoding UTF-8.
\end{itemize}
\section{Recommended Items}
UTF-8 is typically the default on Linux machines, but not on all
Unix machines, nor on Windows, so you must take some care to ensure
that your locale is set properly before starting Bacula.
+On most modern Win32 machines, you can edit the conf files with {\bf
+notebook} and choose output encoding UTF-8.
To ensure that Bacula configuration files can be correctly read including
foreign characters the {bf LANG} environment variable
-2.1.8 (16 May 2007)
+2.1.10 (18 May 2007)