'Defining Content > Document Type Localization' V16 update #7343
Conversation
There was a problem hiding this comment.
Hello @Lili-Rossiter !
I have read through the document and left a few suggestions/questions to maybe make a few points a little clearer. but it's basically great already😁
|
|
||
| * Create the localizations in [user defined backoffice localization file](../../../customizing/foundation/localization.md). | ||
| Setting up localization for Document Types is a three-step process: | ||
| * Register the Document Type localization Files via [a new manifest 'umbraco-package.json' file](../../../customizing/extending-overview/extension-types/localization.md#registering-localization). |
There was a problem hiding this comment.
I would write the word Files without capital letters.
| {% endhint %} | ||
|
|
||
| The Umbraco backoffice is localized to match the [user's configured language](../users/README.md). | ||
| The Umbraco backoffice is localized to match the [user's configured UI Culture](../../../tutorials/multilanguage-setup#changing-the-default-backoffice-language-of-a-user). |
There was a problem hiding this comment.
Strangely enough, the link is displayed as an external link and gives a 404 when you click on it, while the one below on line 17 is OK. The only difference I could spot is the missing .md extension at the end of the main file name, could that be it?
Cf. screenshot: the url links to githuib instead of umbraco docs
| The Umbraco backoffice is localized to match the [user's configured language](../users/README.md). | ||
| The Umbraco backoffice is localized to match the [user's configured UI Culture](../../../tutorials/multilanguage-setup#changing-the-default-backoffice-language-of-a-user). | ||
|
|
||
| When defining a Document Type, you can apply localization to: |
There was a problem hiding this comment.
Maybe a global suggestion for the last 3 bullet points below: we have a strange mix of singular and plural IMHO. I would either leave the element singular and then what follows also singular, either all plural.
So for example, for the second bullet:
Property name and description or Properties names and descriptions
I hope this makes sense ? 😅
| {% endhint %} | ||
|
|
||
| {% code title="umbraco-package.json" %} | ||
| ```json |
There was a problem hiding this comment.
It is not very clear to me if there are parts in the manifest where I have to use the actual alias of the associated document type, or if I need to use specifically the generic term DocumentType.
For example, if I am localizing my custom document type named MikeDocumentType, what do I have to specifiy as alias: DocumentType.Localize.En as written currently, or MikeDocumentType.Localize.En ?
There was a problem hiding this comment.
OK, I just opened the linked docs mentioned above 😅 and it seems to be indeed the actual document type name that needs to be used. I would suggest to then maybe reflect it in the sample for more direct clarity?
There was a problem hiding this comment.
@mikecp Localization works with keys like in the 'old' backoffice. There is no connection to your content type and the registration of the language file. The alias needs to be unique, that's it.
| * Add a new **group** called `#groups_titles`. | ||
| * Add a **property** called `#properties_title` with **alias** `title`. | ||
| * Set description to `{#properties_title-desc}`. | ||
| * Set the description to `{#properties_title-desc}`. |
There was a problem hiding this comment.
Just making sure that it is normal that it's the only place where we use {} around the #area_key part.
There was a problem hiding this comment.
@mikecp it is. The descriptions support Umbraco Flavoured markdown, so that's why the { } are needed.
3 participants
📋 Description
📎 Related Issues (if applicable)
#7342
✅ Contributor Checklist
I've followed the Umbraco Documentation Style Guide and can confirm that:
Product & Version (if relevant)
V16
Deadline (if relevant)
NA
📚 Helpful Resources