V15: Document Type Localization updates

[leekelleher]

Description

Updates the Document Type Localization documentation with relevant details for Umbraco 15 and UFM syntax for localizing property descriptions.

FYI, I've manually updated (a la photoshopped) a couple of the screenshots with the updated UFM syntax, (it was quicker for me to do this than recreating a working Umbraco solution for the article, apologies).

Resolves #6811.

Type of suggestion

• Typo/grammar fix
• Updated outdated content
• New content
• Updates related to a new version
• Other

Product & version (if relevant)

Umbraco CMS 15.0.0

Deadline (if relevant)

As soon as possible.

[eshanrnh]

Hi @leekelleher 👋,

Thanks for updating the article. I tested the changes, but the localized values are not displaying in the backoffice as expected.

Attached a copy of the localization file:

Could you take a look and let me know if the files are placed in the wrong folder or if any adjustments are needed for the localizations to work?

[eshanrnh]

Unfortunately, the localized content is not displayed. This is what I see:

[leekelleher]

Thank you @eshanrnh. I'll take a look this afternoon.

[leekelleher]

Hi @eshanrnh, could you try moving the umbraco-package.json manifest file to the folder above, e.g. /App_Plugins/MyPackage/umbraco-package.json?

The umbraco-package.json files aren't registered for further nested folders. They are only scanned at /App_Plugins/ and /App_Plugins/{YourPackageName} levels.

[eshanrnh]

That works, @leekelleher 🙌 Thanks for helping out. Much appreciated 🌟 I'll merge this PR in and create another PR to update the screenshots and add a Note about the umbraco-package.json file structure.

[leekelleher]

Running through the rest of the guide, I'd noticed that the v15 backoffice code doesn't support dashes in the localization key/name in particular use-cases, e.g. #contentTypes_article-desc in the Content Create modal.

In the code, the issue is related to word boundaries, where a dash is used to separate words, whereas an underscore is considered part of the word. I'll chat with the team to see whether we still want to support dashes, or if we replace the dashes with in underscores in the documentation.

[eshanrnh]

I noticed that too, but you were quick to catch it and let me know! 😊 Appreciate you looking into it—let me know what the team decides, and I can update the documentation accordingly (or you can - whatever works best) 🙌