diff --git a/.env.example b/.env.example index c3cc17d0..a0aebb6b 100644 --- a/.env.example +++ b/.env.example @@ -1,5 +1,6 @@ NUXT_PUBLIC_TRANSLATE_API= NUXT_PUBLIC_DEFAULT_SERVER= +NUXT_PUBLIC_PRIVACY_POLICY_URL= # Production only NUXT_CLOUDFLARE_ACCOUNT_ID= diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a629b3c9..a2bae242 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -93,17 +93,17 @@ We are using [vue-i18n](https://vue-i18n.intlify.dev/) via [nuxt-i18n](https://i 1. Add a new file in [locales](./locales) folder with the language code as the filename. 2. Copy [en-US](./locales/en-US.json) and translate the strings. -3. Add the language to the `locales` array in [config/i18n.ts](./config/i18n.ts#L12), below `en` and `ar`: +3. Add the language to the `locales` array in [config/i18n.ts](./config/i18n.ts#L61), below `en` and `ar`: - If your language have multiple country variants, add the generic one for language only (only if there are a lot of common entries, you can always add it as a new one) - - Add all country variants in [country variants object](./config/i18n.ts#L97) + - Add all country variants in [country variants object](./config/i18n.ts#L12) - Add all country variants files with empty `messages` object: `{}` - Translate the strings in the generic language file - - Later, when anyone wants to add the corresponding translations for the country variant, you can override all entries in the corresponding file: check `en` (english variants), and override the entries in all country files, if you omit them, `i18n` module will use the language entry. You will need also copy from base file to the rest of country variants those messages not being shared (the Elk team is working on resolving this, assuming it can be resolved). + - Later, when anyone wants to add the corresponding translations for the country variant, just override any entry in the corresponding file: you can see an example with `en` variants. - If the generic language already exists: - If the translation doesn't differ from the generic language, then add the corresponding translations in the corresponding file - If the translation differs from the generic language, then add the corresponding translations in the corresponding file and remove it from the country variants entry -4. If the language is `right-to-left`, add `dir` option with `rtl` value, for example, for [ar](./config/i18n.ts#L22) -5. If the language requires special pluralization rules, add `pluralRule` callback option, for example, for [ar](./config/i18n.ts#L23) +4. If the language is `right-to-left`, add `dir` option with `rtl` value, for example, for [ar](./config/i18n.ts#L71) +5. If the language requires special pluralization rules, add `pluralRule` callback option, for example, for [ar](./config/i18n.ts#L72) Check [Pluralization rule callback](https://vue-i18n.intlify.dev/guide/essentials/pluralization.html#custom-pluralization) for more info. diff --git a/components/account/AccountHeader.vue b/components/account/AccountHeader.vue index 8cb40f83..233c96d4 100644 --- a/components/account/AccountHeader.vue +++ b/components/account/AccountHeader.vue @@ -117,6 +117,20 @@ const isNotifiedOnPost = $computed(() => !!relationship?.notifying) + + + + + + () const account = props.account || (props.handle ? useAccountByHandle(props.handle!) : undefined) +const userSettings = useUserSettings() + defineOptions({ inheritAttrs: false, })