Lingo Provider
A Vapor provider for Lingo - a pure Swift localization library ready to be used in Server Side Swift projects.
Setup
Add a dependancy
Add LingoProvider as a dependancy in your Package.swift file:
dependencies: [
...,
.package(name: "LingoVapor", url: "https://github.com/vapor-community/lingo-vapor.git", from: "4.2.0")]
],
targets: [
.target(name: "App", dependencies: [
.product(name: "LingoVapor", package: "LingoVapor")Upgrading from version 4.1.0 to version 4.2.0
The version 4.1.0 uses the new version of Lingo where the format of locale identifiers was changed to match RFC 5646. Prior to 4.2.0 _ was used to separate language code and country code in the locale identifier, and now the library uses - as per RFC.
If you were using any locales which include a country code, you would need to rename related translation files to match the new format.
Add the Provider
In the configure.swift simply initialize the LingoVapor with a default locale:
import LingoVapor
...
public func configure(_ app: Application) throws {
...
app.lingoVapor.configuration = .init(defaultLocale: "en", localizationsDir: "Localizations")
}The
localizationsDircan be omitted, as the Localizations is also the default path. Note that this folder should exist under the workDir.
Use
After you have configured the provider, you can use lingoVapor service to create Lingo:
let lingo = try app.lingoVapor.lingo()
...
let localizedTitle = lingo.localize("welcome.title", locale: "en")To get the locale of a user out of the request, you can use request.locale. This uses a language, which is in the HTTP header and which is in your available locales, if that exists. Otherwise it falls back to the default locale. Now you can use different locales dynamically:
let localizedTitle = lingo.localize("welcome.title", locale: request.locale)When overwriting the requested locale, just write the new locale into the session, e.g. like that:
session.data["locale"] = localeUse the following syntax for defining localizations in a JSON file:
{
"title": "Hello Swift!",
"greeting.message": "Hi %{full-name}!",
"unread.messages": {
"one": "You have one unread message.",
"other": "You have %{count} unread messages."
}
}Locale redirection middleware
In case you want to serv different locales on different subfolders, you can use the LocaleRedirectMiddleware.
Add in configure.swift:
import LingoVapor
// Inside `configure(_ app: Application)`:
app.middleware.use(LocaleRedirectMiddleware())Add in routes.swift:
import LingoVapor
// Inside `routes(_ app: Application)`:
app.get("home") { /* ... */ }
app.get(":locale", "home") { /* ... */ } // For each route, add the one prefixed by the `locale` parameterThat way, going to /home/ will redirect you to /<locale>/home/ (with <locale> corresponding to your browser locale), and going to /fr/home/ will display homepage in french whatever the browser locale is.
Inside Leaf templates
When using Leaf as templating engine, you can use LocalizeTag, LocaleTag and LocaleLinksTag from LingoVaporLeaf for localization inside the templates.
Add in configure.swift:
import LingoVaporLeaf
// Inside `configure(_ app: Application)`:
app.leaf.tags["localize"] = LocalizeTag()
app.leaf.tags["locale"] = LocaleTag()
app.leaf.tags["localeLinks"] = LocaleLinksTag()Afterwards you can call them inside the Leaf templates:
<!-- String localization -->
#localize("thisisthelingokey")
#localize("lingokeywithvariable", "{\"foo\":\"bar\"}")
<!-- Get current locale -->
<html lang="#locale()">
<!-- Generate link canonical and alternate tags -->
#localeLinks("http://example.com/", "/canonical/path/")Learn more
- Lingo - learn more about the localization file format, pluralization support, and see how you can get the most out of the Lingo.