Don't require i18n source files for all plugins to be encoded

Description

It was already done for regular translation files, but almost every plugin has its own i18n files which still has to be edited using \uxxxx substitutions. Should be fixed also.

Environment

None

Linked work items

is related to

OF-1448

Don't require i18n source files to be encoded.

OF-1516

Convert Russian translation for Registration plugin to unicode

OF-1500

Monitoring plugin's menus garbled when using Russian language

relates to

OF-2889

i18n properties: don't convert from UTF-8 to Latin1

Activity

Resize work item view side panel

Fixed

Details

Assignee

Guus der Kinderen

Reporter

wroot

Priority

Minor

Created March 17, 2018 at 12:16 PM

Updated January 4, 2025 at 7:30 PM

Resolved October 19, 2018 at 4:53 PM