Testing the translation worked out fine and the Finnish strings should now be okay for the most part at least. Here are some miscellaneous observations I made while checking the translation:
Client:
- The About popup menu item seems to use the Infos string meant for the log filter instead of the string that is used in e.g. the About window title.
- The date, time and percentage formats do not seem to be localizable.
- The OK and Cancel button texts don’t seem to be localizable.
- Finnish words can get quite long but the windows do not scale, so I had to shorten quite a few strings by removing words that are kind of implied by context. For example, some file backup setting labels do not restate that they are about file backups since that is implied by the tab in the UI. These may become ambiguous if the labels are moved to a different context.
Server:
- “With Selected” in Backup Status is not localizable.
- The Show/hide columns flyout items do not fit in the panel; this affects English as well.
- I assume there should be arrows displaying the sort direction of each column in some table, but at least on my machine these show up as placeholder box glyphs with E150, E155 and E156 in them.
- “Volume:” and network speed and storage units in Activities are not localizable. (Also, the Volume label is shown even if there’s no volume involved, but that’s not a localization issue.)
- The Finnish words for time units in Settings > Archive do not fit into the drop-downs.
- “Full image backup” in Settings > Advanced > Local full image style should be localizable distinctly from the general “Full image backup” string because that string does not make very good sense in this context in Finnish.
- “Administrator” in Settings > Users > Edit > Rights for should preferrably be distinct from “Administrator” shown in the Settings > Users table.
- Because some words are quite long (e.g. “Tiedostomuutosvarmuuskopio” for incremental file backup), it could be useful to be able to insert soft hyphens in some of the longer words. In HTML that can be achieved using the ­ entity but entities seem to get escaped. Would it be possible to include special cases e.g. for ­ and (unless of course there is already a way to do that)?