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
Dyn365GP19 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Rename a Company
Dyn365GP18 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Share a Saved List View
Dyn365GP17 April 2024Splitting a Table on a Microsoft Dynamics 365 Business Central Word Template
Dyn365GP16 April 2024Preview of Microsoft Dynamics 365 Business Central 2024 Wave 2 Investment Areas
