[cvs] [Wiki] changed: FAQ/Admin/Config

[Jan Schneider]

jan  Mon, 17 Sep 2007 08:29:45 -0700

Modified page: http://wiki.horde.org/FAQ/Admin/Config
New Revision:  4.15
Change log:  Remove old information

@@ -76,20 +76,22 @@
 $conf['cookie']['path'] = '/';
 </code>

 +++ How can I change the appearance?
-**[Horde 2.0]:** For Horde 2.x and its components, configure the settings
in {{/horde/config/html.php}} and in
{{/horde/componentname/config/html.php}}. The settings for various colours,
fonts, and styles are found within, with explanatory comments and variable
names.
+**[Horde 2.x]:** For Horde 2.x and its components, configure the settings
in {{/horde/config/html.php}} and in
{{/horde/componentname/config/html.php}}. The settings for various colours,
fonts, and styles are found within, with explanatory comments and variable
names.

 In Horde 2.x, you can add Horde modules to the bottom Horde navigation bar
by modifying {{/horde/config/registry.php}}. This is not as easy or flexible
as the Horde 1.x method above.

 You can modify most Horde 2.x components' navigation bars (at the top of
screen) by similarly modifying the {{/horde/componentname/config/menu.php}}
file. Follow the instructions in the comments found in the file. This
provides a very easy way to add links to the various Horde component
navigation menus.
+
+**[Horde 3.x]:** See ((Doc/Dev/Layout)) and ((Doc/Dev/Themes)).

 +++ How can I change the phrases used for various features?
 You may wish to alter some of the text in an existing language -- to match
the terminology used locally, for instance.

-**[Horde 2.x]:** In Horde 2.x, you change strings by changing them in the
locale files for the desired language(s). To change the US English
translation, you will need to create a new US English (en_US) locale, as one
normally does not exist, and modify the translations in that file. See the
following FAQ entry for information on creating a new locale file.
+You change strings by changing them in the locale files for the desired
language(s). To change the US English translation, you will need to create a
new US English (en_US) locale, as one normally does not exist, and modify
the translations in that file. See the following FAQ entry for information
on creating a new locale file.

-To change the translation for a locale, you must first change the locale
files and then recompile them. Find the appropriate files in {{/horde/po/}},
named by the locale name. Edit the translation(s) in this file to suite your
needs. Then compile the locale files using the provided Makefile. For Horde
2.x components, follow the same steps using the {{/horde/componentname/po}}
files.
+To change the translation for a locale, you must first change the locale
files and then recompile them. Find the appropriate files in {{/horde/po/}},
named by the locale name. Edit the translation(s) in this file to suite your
needs. Then compile the locale files as described in your version's
{{/horde/po/README}} file. For other components, follow the same steps using
the {{/horde/componentname/po}} files.

 If you are having difficulty finding the file which contains the phrase you
want to change, the following Unix command may be of assistance:

 <code>
@@ -102,20 +104,9 @@

 Note: The following question may also be of help to you if you are changing
the locale files.

 +++ How can I provide another translation for Horde/IMP's messages?
-**[Horde 2.x]:** Horde 2.x uses GNU gettext for internationalization (i18n)
and localization (l10n). See {{horde/po/README}} for more information.
(Since Horde 2.2 this information is instead located at
{{[http://www.horde.org/horde/docs/?f=TRANSLATIONS.html
horde/docs/TRANSLATIONS]}})
-
-To create a new translation:
-
-# Go to the {{horde/po}} directory (for other components go to
{{horde/componentname/po}})
-# run {{xgettext.sh}} to generate a {{messages.po}} file
-# rename the {{messages.po}} file base on the language you are using. For
example, for Dutch (nl_NL) you would rename the file to {{nl_NL.po}}
-# Adjust the header lines (dates, authors, etc) of the file, and remove the
first **#, fuzzy** line
-# Translate the text in the //msgid// lines into the appropriate //msgstr//
lines.
-# Compile the new file using the included makefile ({{make install}})
-# If the language does not already exist in {{horde/config/lang.php}} add
any required entries for it in that file. You may want to add a two-letter
alias for the language, and if it uses a non-ascii character set you should
define that also in the {{$nls['charsets']}} array.
-# Mail your new translation to [mailto:i18n at lists.horde.org the developers]
so that we can include it in the distribution!
+Horde uses GNU gettext for internationalization (i18n) and localization
(l10n). See {{horde/po/README}} and
{{[http://www.horde.org/horde/docs/?f=TRANSLATIONS.html
horde/docs/TRANSLATIONS]}} for more information.

 +++ How do I let users report problems directly from Horde?
 Horde comes with a problem-reporting form. You can control who sees it, and
what is done with problem reports, by going to the //Problem Reporting// tab
of the Horde Configuration tool.