missing text string in localization files
We've been working on French translations of all the text strings used in Essentials but today I ran into one that seems to be hard-coded somewhere in the 2.4 viewer.
If you run a search in the viewer and get the results listed in the frame on the left of the screen, there is a menu button in the results frame header that you can click on to switch to table view, export data, etc.. When you mouse over this button, you see the text "Panel Actions Menu: Click to Open/Close". I have searched everywhere for this text string and can't find it anywhere - it's not in the desktop.json.js nor any localization files. I looked at the ResultsListActions section in the desktop.json.js file and there is a description parameter which points to a localized text string called @language-menu-results-list-actions-desc but that string does not exist in any usual locale files. I did find it in a file called invariant.json but it contains the text "Results List Actions" - not the text that shows up in the browser (see above). Does anyone know what this invariant.json file is used for?
Has anyone run into this issue before? There are likely additional strings like this - for sure the ResultsTableActions has the same behaviour. We really need to track these strings down in order to be able to publish any public apps - they have to be French and English.
Peter.
-
Peter,
The string you're looking for is actually "Panel Actions Menu. Click to open/close." - notice the dot (.) instead of a colon. The language string you need to update is "language-smart-panel-menu", it is in Mapping.Infrastructure.en-US.json
Hope this helps,
--Alejandro
0 -
Thanks Alejandro,
I think it was my mistake :(
This site was upgraded from 2.3 and I think I must have copied the old Mapping.Infrastructure.en-US.json.js file over by mistake at some point. I unpacked the VTE file again and there is was... along with about 30 other new lines of text. That might explain a few things!Thanks for the quick response.
Peter.
0
Please sign in to leave a comment.
Comments
2 comments