Page MenuHome

Strange translation text behaviour
Closed, ResolvedPublic

Description

OS: Linux mint 19.1
Kernel: 4.15.0-20-generic x86_64

Graphics:
Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Hewlett-Packard
Device-2: NVIDIA GK208M [GeForce GT 740M] vendor: Hewlett-Packard

Blender version:
Blender 2.80 (sub 74)
build date: 2019-07-03
build time: 02:04:42
build commit date: 2019-07-02
build commit time: 22:33
build hash: 50ccbe6bb233
build platform: Linux

Played a little with Physics and noticed a little strange behaviour on this screen:

When switched to Vietnamese and vary the 'Cache Step' (from 1 to 4 says) - using mouse pointer clicking the little arrow at each end of the control to in/decrease the value - notice the text '1 frames in memory (204 B).' changing erratically from Vietnamese to English and back. Here is an example:

At frame 1

To frame 4

I'm attaching the blender file used for testing and the 'blender.mo' for the Vietnamese translation I'm using. Drop the 'blender.mo' for Vietnamese at the location '~/2.80/datafiles/locale/vi/LC_MESSAGES' before changing the interface to Vietnamese (enable only the 'tooltips and interface').

Event Timeline

Please use the bug submission form when reporting bugs, do not create custom tasks.
https://developer.blender.org/maniphest/task/edit/form/1/

Germano Cavalcante (mano-wii) lowered the priority of this task from Needs Triage by Developer to Normal.

A guideline for making a good bug report can be found here: https://wiki.blender.org/wiki/Process/Bug_Reports

@Bastien Montagne (mont29), you've been working in this area recently.
It's also possible to reproduce the bug with some other languages (like Spanish).

Bastien Montagne (mont29) triaged this task as Confirmed, Low priority.Jul 3 2019, 4:42 PM

Issue happens because that info is often generated by worker threads (instead of main one used by UI code), and boost i18n code does not work well from threads (here it just return unstranslated string it'd seem).

Will check on how to always generate that info from main thread (using probably some dirty tag + generate-on-access mechanism), but would not consider this a top priority issue. ;)