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
- Dyn365GP26 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Restore an Environment to a Point in Time
- Dyn365GP25 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Restore a Deleted Environment
- Dyn365GP24 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Delete an Environment
- Dyn365GP23 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Delete a Company