Hofer Ivan

The bug is located in this function: https://github.com/sveltejs/svelte-preprocess/blob/main/src/modules/globalifySelector.ts#L11 The `Regex` does not account for more modern `:where`, `:not` and `:ìs` selectors

Hi @samuelstroschein, very detailed write-down 👏. Here are some comments on the points of th RFC: ## Human Language Syntax I would choose **Proposal A**, if it supports already >...

> I take from your remarks that inlang is headed in the right direction? Everything you have described above aligns with the [`long-term-goals`](https://github.com/ivanhofer/typesafe-i18n/discussions/324) of `typesafe-i18n`, so yes, I think you...

@terales any updates? :)

Hi @terales have you had time to take a look at this PR? :)

Hi @terales, thanks! What exactly do you mean with "keys as strings"? The keys are already detected, but the issue is that the language files are not detected.

@Juici wow, looks really cool 👍 I will try it on some of my projects the next days

@Juici I have tweaked the config a bit and this is now the config I use: `.vscode/settings.json` ```json { "i18n-ally.pathMatcher": "{locale}/index.{ext}", "i18n-ally.enabledParsers": ["ts", "js"], "i18n-ally.keystyle": "nested", "i18n-ally.localesPaths": ["src/i18n"] } ```...

There is an open PR for this issue: #681

Thanks, I now understand the problem better. So the propreocessor structure would need to be updated to be able to distinguish between "regular" preprocessors and preprocessors that make TypeScript changes?...