- changed status to open
Array elements are missing in xlf file when json type of file is used
Hello,
We have tried to convert json file to xlf, but the array elements are not present in the xlf.
The example json is attached and the missing strings are "chair" and "book".
Thank you
Dragana Gligorovska
Comments (7)
-
-
@Dragana Gligorovska
By default the JSON filter will not extract values that don’t have a unique associated key. You can change this behavior with the fprm setting:
extractIsolatedStrings.b=true
-
reporter @jhargrave-straker the setting is already there, but we have issue, it is not read by rainbow for some reason. Do you maybe could help regarding that? Thank you!
-
reporter We tried to test this feature with Okapi Rainbow, but it seems like it doesn't load the custom configurations, even though they are listed under Tools > Filter Configurations.
Default custom parameters folder is also set under User Preferences.
The content of the custom file is:#v1 extractIsolatedStrings.b=true extractAllPairs.b=true exceptions= useKeyAsName.b=true useFullKeyPath.b=false useLeadingSlashOnKeyPath.b=true escapeForwardSlashes.b=true useIdStack.b=false useCodeFinder.b=false noteRules= extractionRules= idRules= genericMetaRules= codeFinderRules.count.i=1 codeFinderRules.rule0=</?([A-Z0-9a-z]*)\b[^>]*> codeFinderRules.sample=&name; <tag></at><tag/> <tag attr='val'> </tag="val"> codeFinderRules.useAllRulesWhenTesting.b=true subfilter= subfilterRules=
-
reporter We have solved the issue with setting the setExtractStandalone(true) parametar. Should we open another ticket for the rainbow issue?
-
Maybe you can post on the user mail group about the Rainbow issue - if you can’t find a solution then please create a new ticket for Rainbow. Thank you!
-
- changed status to resolved
- Log in to comment