How to implement different implementation of ILanguageGateway?

Topics: Developer Forum
Apr 9, 2009 at 8:28 PM
Hi,

We have some fundamental issues with the N2.Engine.Globalization.LanguageGateway class: It forces a specific site structure that is not compatible with our existing websites which we are converting to N2. Further, multiple language roots with the same Language Code cause the possibility to translate one page to the exact same language multiple times; an illogical possibility.

My team therefore would like to create a seperate ILanguageGateway implementation that allows an arbitrary structure for translations so we are not forced into a structure by N2. We have stubbed out a class we think will work, but we do not  know how to "plug in" to N2 with it. Is there something in the Web.Config we can set to use our version of ILanguageGateway instead of the one built-in to N2?

Once we get it working, we will be happy to donate it to the project. We feel this flexibility with URL structures is extremely important, especially if N2 is to be adapted to existing sites.

Thanks -

-James
Apr 13, 2009 at 7:06 PM
Bump!
Apr 14, 2009 at 3:43 AM
<n2>
        <engine>
            <components>
                <add service="N2.Engine.Globalization.ILanguageGateway" implementation="CustomLanguageGateway, Assembly"/>
            </components>
         <engine>
<n2>