This post is part of the sub-series on Internationalizing a ClassicPress plugin which is part of the Internationalizing a ClassicPress plugin series.
When internationalizing a plugin, you should, as far as possible, avoid including HTML markup in the localization strings.
Annoyance the First: Thou shalt not put unnecessary HTML markup into the translated string. For example, a heading should…
Continue Reading Ian Grieve’s Article on their blog
Internationalizing a ClassicPress plugin: Don’t include HTML markup in localization
This post is part of the sub-series on Internationalizing a ClassicPress plugin which is part of the Internationalizing a ClassicPress plugin series. When internationalizing a plugin, you should, as far as possible, avoid including HTML markup in the localization strings. Annoyance the First: Thou shalt not put unnecessary HTML markup into the translated string.
Blog Syndicated with Ian Grieve’s Permission
More About This Author
Array
- Dyn365GP7 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Improvement of Czech Localization Reports
- Dyn365GP7 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Process Czech Bank Statements, Payment Orders More Productively
- Dyn365GP6 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Use a New Role Center for Collection Management
- Dyn365GP6 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Ensure Accurate Inventory Valuation by Controlling Cost Adjustment