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 problem

Our translators would like to check for nearby keys and have a button to adopt this translation also for the current string, because it is often the same.
Instead, when they try to copy it, the user gets redirected to the string and the last translation is gone.

Describe the solution you'd like

A Button to adopt the nearby translation for the current string (se

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 #1694 I added is_ascii_lowercase() (and uppercase and titlecase). The functions are defined to mean that if you apply to_ascii_lowercase() (or uppercase/titlecase), then you get back the same string.

However, many call sites are ending up looking like

s.is_ascii_alphabetic() && s.is_ascii_lowercase()

I think we should add functions that combine both checks and save a