[TYPO3-dev] Content Fallback and URL

[Frans Saris]

Hi Dmitry,

2013/8/30 Dmitry Dulepov <dmitry.dulepov at gmail.com>

> Hi!
>
>
> Gion Koch wrote:
>
>> Now, the customer doesn't like the behaviour when you are on a 1st Level
>> page and switch to another 1st level page, with a different language
>> setup, that the specific language segment in the url( /en/ ) from the
>> Realurl extension doesn't get changed to the fallback language.
>>
>
> I only comment about RealURL.
>
> RealURL gets something like /index.php?id=15&L=2. It _only_ translates
> parameters to speaking segments. If L is 2 and 2 is English, there will be
> /en/ because TYPO3 core asked for this. You get what the core asked. No
> magic of any kind, no guessing, just plain <strike>stupid</strike>
> straightforward one to one translation from query string to path.
>
>
And how does the translation of the page happen when content_fallback is
used?
for instance:
we have English, Canadian and French as localisations. English is the base
localisation (id=0), French is also a 'base' language and Canadian has
French as fallback.
Now for a certain page there is no Canadian translation so the French
translation is served. Does realurl then also use the fallback translation
to create the query string?

gr. Frans