in reply to Multi-language websites: any advice?

I rather like the approach outlined in Re: Multilingual design - did you see that?

produce the various other webpages living in /en/index.html, /fr/index.html, etc.

Do consider using MultiViews instead of (or at least in addition to) this. It's a much more elegant solution, IMHO.


🦛

Replies are listed 'Best First'.
Re^2: Multi-language websites: any advice?
by bliako (Abbot) on Oct 11, 2024 at 16:37 UTC

    thanks I have not seen that. From what I understand, it "translates" the page every time it is served. I need to clarify that I am looking for a system which manages the translation and creates translated pages ready to be served. Once created there is no translation on these pages. When new content is added to the "mother" page, the system re-creates all the translated pages. I need => I think it is more efficient for the server.

      Yes, it translates on every serve. That allows to use the translation tool integrated into the website. In my case, all translations are cached in RAM, so this is reasonably fast. It takes up only a small fraction of the time needed to serve a completed document. There are also authentication checks, flood checks, bot checks, database access, logging, compression for network transport and a multitude of other things that have to happen when you serve highly dynamic content on a public server.

      So, at least in my case, on-the-fly translations really don't really make much of a difference...

      Of course, nobody is stopping you from putting your documents through TT and caching the results.

      PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
      Also check out my sisters artwork and my weekly webcomics