I am working on a site that has EN and ES - I got the home page translation to work by putting in the same path for both pages on the edit page. I had to translate all the blocks separately- so it's almost all good except on the ES home page, the ES translated block will not display - it only shows the English block. I have a feeling it is because of the "same path" issue. Does anyone have any clues on this?
To me and my potential users, English is good enough for the overall interface. So I am not interested in translating the whole site. But when I use a CCK date field, I cannot use a long date format and have the names of the day or the month shown in a non-English language (Danish).
Hi guys,
is it possible to import the "po" files just in the folder of the module that I have to translate without import it with "Translate interface"?
This should be simple. I started a web site with the default language as English, and have now switched it to German as the default, but the language negotiation still uses example.com/de for German language nodes, and example.com for Engish nodes.
What I would like to do is to have English nodes come up with example.com/en, and the German nodes with plain example.com.
I am not scared of doing a bit of SQL, if that will get me there.
It does not seem doable.
I have tried to reverse engineer why it doesn't work.
sizeof($custom_strings[$langcode])=0 in my block
that is e.g. t('January') returns 'January' even though I selected another language, which works everywhere else on the site :-\