You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Localized resources might contain simple HTML markup. One might argue that HTML should not be in resources at all, and message should be formed from separate pieces.
In most cases it would add huge overhead and would not make sense for resource editors as they would loose context of each translation piece and how they fit together.
Example:
[LocalizedResource]
public static class MyResources
{
public static string StatusMessage => "Inserted <b>{0}</b> records, updated <b>{1}</b> records.";
}
For such cases rich editor might be helpful as for regular resources (without HTML tags) it would render as usual.
The text was updated successfully, but these errors were encountered:
Localized resources might contain simple HTML markup. One might argue that HTML should not be in resources at all, and message should be formed from separate pieces.
In most cases it would add huge overhead and would not make sense for resource editors as they would loose context of each translation piece and how they fit together.
Example:
For such cases rich editor might be helpful as for regular resources (without HTML tags) it would render as usual.
The text was updated successfully, but these errors were encountered: