2 results found

1. getSystemPath using CSInterface throws URI Malformed error

   I was trying to get the my documents folder path of the system using CSInterface getSystemPath function. It works in most of the cases. But it throws URI malformed error (refer the screenshot below), if the path of the documents folder contain characters from languages other than English.

   I debugged the CSInterface.js file at line 521. And I found that the below piece of code returns the path of the folder without encoding the characters from languages other than English.

   window.adobe_cep.getSystemPath(pathType)

   IN MY CASE:

   Path of documents folder: "C:\Users\sanjay\OneDrive - Élégante\Documents".

   window.adobe_cep.getSystemPath(pathType)
   // Returned value - "file:///C:/Users/sanjay/OneDrive%20-%20Ã%89lÃ%a9gante/Documents"
   // É is encoded as Ã%89

   encodeURI("C:/Users/sanjay/OneDrive - Élégante/Documents")
   // Expected value - "file:///C:/Users/sanjay/OneDrive%20-%20%C3%89l%C3%A9gante/Documents"
   // É is encoded as %C3%89

   decodeURI("Ã%89") throws URI malformed error.
   decodeURI("%C3%89") returns É.

   ISSUE:

   So, I guess it is the problem with the encoding of window.adobe_cep.getSystemPath(pathType). Is there any work around for this issue?

   SAME ISSUE WITH OTHER FUNCTION:

   I'm also facing the same issue with other scripting functions like "documentAfterActivate" CS Event which returns the path of active document if a document is opened. The path received is not encoded properly for characters other than English.

   VERSION INFO:

   CEP: 9
   InDesign: 2022
   OS: Windows 10

   I was trying to get the my documents folder path of the system using CSInterface getSystemPath function. It works in most of the cases. But it throws URI malformed error (refer the screenshot below), if the path of the documents folder contain characters from languages other than English.

   I debugged the CSInterface.js file at line 521. And I found that the below piece of code returns the path of the folder without encoding the characters from languages other than English.

   window.adobe_cep.getSystemPath(pathType)

   IN MY CASE:

   Path of documents folder: "C:\Users\sanjay\OneDrive - Élégante\Documents".

   window.adobe_cep.getSystemPath(pathType)
   // Returned value -… more

   •  

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  CEP  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. PreflightScope not working

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’ and ‘1,2’)

   We would very much like to speed our preflight process and get rid of the tedious parsing of preflight results only to discard pages not set in the scope.

   One additional note on its behavior that could be fixed, too: if you define a scope that includes page numbers not in the document, either as
   - a range e.g. "1-5" when document has pages numbers 1,4,5,6,... or
   - e.g. "14" when the document has only 12 pages
   ––> InDesign throws an error "Error 30477: Invalid value for set property 'preflightScope'. Expected PreflightScopeOptions enumerator or String, but received "1-5".", which is quite misleading.

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’… more

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  CEP  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Under Review  ·  amaarora responded

   Thanks for reporting
   We are reviewing the issue

   -InDesign Team