none (user conﬁgurable)
kills pathauto if you aren't careful (stay far away from this option)
path preﬁx with language fallback (total confusion)
path --> user conﬁgured (from account page) --> browser's default
language --> default site language (which means a mess of
determined by selected language on node/edit page; language neutral shows on ALL
will show only on speciﬁed page
will default to default language, or rather, the current admin language
*** even if you declare an item to be spanish, 'translation interface' will consider it english
because that was your current admin language!! ****
per content-type enable support under 'Workﬂow
by default, all existing nodes in this content type will
be 'language neutral', meaning they will appear in ALL
Change any nodes to being a speciﬁed language
this will allow for the "translate" tab, as well as
"translation overview" to manage translations
When Translating, a copy of the default text will occupy
the ﬁelds, (even CCK!), now you can replace them
user created blocks
All languages (with translations)
module created blocks
no translations :(
views created blocks
no translations :(
there's a patch!
user created menu items
negotiations are determined by the node in which it links
external links do not contain language negotiations, so
they will appear everywhere!
requires work around!
node generated menu items
negotiation is based on node language, then global
view generated menu items
can be assigned to speciﬁed menu, they can be
translated, however, they will appear on every language!!
requires work around
$conf['i18n_variables'] = array(
// Site name, slogan, mission, etc..
// Different front page for each language
// Primary and secondary links
// Contact form information
MORE ON VARIABLES
Any variables declared here will override whatever is in the variables
You will notice on the admin ﬁelds there will be a
disclaimer stating that "THIS IS A MULTILINGUAL
VARIABLE' warning you that it will be assigned only to the
currently logged in language
works with an i18n ﬁlter
this means you don't have to declare your
nodes to be a speciﬁed language if they are
only intended to be displayed in a view
depends on every other language
nodes displayed by a view through a block
node must be enabled, blocks must be
enabled, view must have language ﬁlter
(otherwise you will get duplicates)
works only with taxonomy, menus, blocks, and views
Search will help track down all title and body (for blocks) (with
the condition that they are set to "ALL LANGUAGES WITH
notice that the untranslated language is crossed out?
these translations are stored on the database
export all translations
export .po ﬁles and edit them on any PO editor
Stay away from REFRESH, only bad things will happen!
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.