Phoenix VerifiedRoutes and routes localization

Phoenix Forum Questions / Help
, , , ,
1

I was reading the Localized routes and path prefixes section of the Phoenix.VerifiedRoutes and I found this line:

In this case, you would have a plug that looks at the host and at HTTP headers and calls Gettext.get_locale/1 accordingly.

It’s not clear to me how this plug should be used.

What I’m trying to achieve is localized routes based on the language, for example:

  • /login for English

  • /accedi for Italian

but without maintaining multiple routers.

Ideally, I would like to define the route once, with all the routes in english, and have the URL automatically translated depending on the locale or domain.

Is this possible with a plug?
Perhaps something like a reverse route translation mechanism?

I also would like to avoid external dependencies.

2

That line is for the case of using the hostname to distinguish between languages - not doing so by path. The text following that paragraph is for when you want to use a path segment to determine the language.

1 Like
3

This is the origin feature of Routex - build powerful Phoenix routes: localize, customize, and innovate

2 Likes
4

@LostKobrakai ok thanks, I was hoping there might be a built-in way to localize routes.

@BartOtten thank you, I already know of Routex, but I’m trying to avoid using external libraries for this.

5

I wonder why? Could you expand on the reasoning? It seems to me that wish leads to unnecessary extra work, but maybe some other requirement overrides the burden.

As Routex core is slim but hardened, you might have at least a peek how it works as you probably need to build something similar :wink:

6

I was hoping for a built-in solution, since I try to keep dependencies to a minimum whenever possible.

I’m familiar with Routex and have been looking through its source code. I like it a lot, but it feels a bit overcomplicated for my current needs. That said, I’m still evaluating my requirements, so I’m not ruling it out for my project.