internationalization

Hello,

I'm using vue-i18n on my nuxt app with typescript.

I have a simple question :
Why in

declare module 'vue/types/options' {
	interface ComponentOptions<V extends Vue> {
		i18n?: {
			messages?: VueI18n.LocaleMessages
			dateTimeFormats?: VueI18n.DateTimeFormats
			numberFormats?: VueI18n.NumberFormats
			sharedMessages?: VueI18n.LocaleMessages
		}
	}
}

`local

Describe the bug
The output PO file has comments with a leading period:

#. Your free trial will end on August 6th and will not renew.
#: src/components/routes/billing/Status/Status.tsx:56
msgid "and will not renew."
msgstr ""

To Reproduce
Steps to reproduce the behavior, possibly with minimal code sample, e.g:

import { t } from "@lingui/macro"

cons

Describe the problem

There is a draft standard to have a standard URL users can navigate to change their password.

https://w3c.github.io/webappsec-change-password-url/

The goal is to make managing passwords easier, so software can help users change their password, browsers can direct them to where they can change their password, and for programmatic access by password managers.

To

https://github.com/traduora/traduora/blob/f921f7c5eab3b96d467a8a8a5dd8dd57f0615ee6/webapp/src/app/shared/components/search/search.component.ts#L21

Search result count is 10.
How can i set the pagesize on user side

If the locale is set using this.translocoLocaleService.setLocale(locale) (or default) it is overwritten the moment this.translocoService.setActiveLang(lang); is called.

Because of the https://github.com/ngneat/transloco/blob/master/projects/ngneat/transloco-locale/src/lib/transloco-locale.service.ts
translocoService.langChanges$ subscription.

There is no property or config to disable

The Problem
The initialization of svelte-i18n sets the preferred language in a global variable.
While this is acceptable for client, it is not acceptable for the server (with SSR).

The server might be async, in which it can proccess at the same time both request for one language and a request for other language.
However, as far as I can see, setting a new locale will override the existin

In #1767 I introduced the concept of ShortVec in Locale, but only for Keywords and Fields.

If we extend the use of ShortVec to other places in Locale that currently use Vec, then we will be able to enable code such as:

locale!("en-US-u-ca-buddhist")
langid!("es-CA-valencia")

and basically any other situation where there is exactly 0 or 1 of everything. It also