Home › Forums › Classic DFFS › Support for language (pt-PT)
Tagged: #language-pt
- This topic has 6 replies, 2 voices, and was last updated 4 years, 6 months ago by Alexander Bautz.
-
AuthorPosts
-
-
June 1, 2020 at 10:26 #30371
Can you please translate the text “You must specify a value for this required field.” to “Campo de preenchimento obrigatório.” in a next update.
Is there in version 4.4.4.25 any way to translate the text through customJS?Attachments:
-
June 1, 2020 at 11:47 #30374
Hi.
Is there a field in the vLookUp configuration where the text “View item” corresponding to the magnifying glass tooltip can be translated?
Attachments:
-
June 1, 2020 at 15:49 #30379
Sure, I’ll change this label in the next release. You can also change it by adding a variable to your custom js as described here: https://spjsblog.com/dffs/dffs-user-manual/#Tips_and_tricks
The view and edit item labels in vLookup can by translated by adding this to your custom js:
var L_ViewItem_Text = "Add View item label here"; var L_EditItem_Text = "Add Edit item label here";
These variables existed in out of the box SharePoint earlier and I wasn’t aware that they no longer was included and therefore the automatic localization of them no longer worked.
Alexander
- This reply was modified 4 years, 6 months ago by Alexander Bautz.
-
June 1, 2020 at 16:17 #30382
Thanks.
Just one more question.
Can these variables be declared in an external JS loaded in MasterPage since the texts are common to all the forms or must they be mandatory declared in each customJS of each form?
-
June 1, 2020 at 16:21 #30384
I’ll get them fixed so that they are automatically localized (based on internal SharePoint localization files) in the next version (maybe later today).
Alexander
-
June 1, 2020 at 16:34 #30387
If I upgrade from version 4.4.4.25 to the latest version, that already has these variable situations, do I have to remove the instructions for the Boolean fields “spjs.dffs.stringToBoolean” from customJS? Will the new version also address the issue of boolean fields?
-
June 1, 2020 at 16:38 #30389
The new version will address that also, but you can keep your code in custom js – it will not interfere with the updated version so you don’t need to remove it.
Alexander
-
-
AuthorPosts
- You must be logged in to reply to this topic.