Skip to main content
KV-Vel
KV-Vel
Participant
March 18, 2026
Answered

Plugin Localization Issue: Handling Non-English API Responses for Adobe Review Approval

  • March 18, 2026
  • 2 replies
  • 33 views

Hello everyone!


I was told by Adobe Review Team to try and post my question here. I’m not entirely sure If it is the right community, because in their email they refered to “Adobe Developer Support Forum” and provided link to this forum.

Issue:

I’ve developed a plugin which integrates spellchecking API into Indesign. However, the API is from a Russian app, and plugin only works with Russian language. 

For plugin review to be successfully completed, It must support English language. I had no problem translating UI into English, but since plugin works with non english API, errors which are sent by an API response are in Russian language and the whole text annotations are also in Russian. I don’t have an access to their server/code to translate every possible error. I didn’t ask devs about this, but let’s say It wouldn’t work… Is It possible to do something about this localization issue? May be there is an easy way to do it? 

Assuming that non english text errors (from API response) is part of the problem, the whole annotation text of the plugin in Russian language would be a much bigger problem, because it would require to localize entire application and may be even more.

 

Thank you!

    Correct answer Manan Joshi

    Is this a C++ plugin? If yes then we generally control/add localisation for strings using the fr file. However, in your case it seems you are saying that the content would be dynamic and got a a result of some 3rd party API calls. I am not sure what can be done for this use case apart from using another 3rd party translation API. Did you confirm with the review team that they are talking about localisation of the plugin UI interface or about everything the plugins adds/does. Because afaik the spelling interfaces you might have tapped will only be triggered and functional when the text language is set to Russian so showing Russian annotations for a Russian text should not be a problem.

    2 replies

    leo.r
    Community Expert
    leo.rCommunity Expert
    Community Expert
    March 18, 2026

    in their email they refered to “Adobe Developer Support Forum” and provided link to this forum

     

    And just in case you need it in the future, developer forums are here:

    https://developer.adobe.com/developer-champion/forums

      M
      Community Expert
      Manan JoshiCommunity ExpertCorrect answer
      Community Expert
      March 18, 2026

      Is this a C++ plugin? If yes then we generally control/add localisation for strings using the fr file. However, in your case it seems you are saying that the content would be dynamic and got a a result of some 3rd party API calls. I am not sure what can be done for this use case apart from using another 3rd party translation API. Did you confirm with the review team that they are talking about localisation of the plugin UI interface or about everything the plugins adds/does. Because afaik the spelling interfaces you might have tapped will only be triggered and functional when the text language is set to Russian so showing Russian annotations for a Russian text should not be a problem.

      -Manan
        KV-Vel
        KV-VelAuthor
        Participant
        March 18, 2026

        I was using Adobe UXP Developer tool (JS). 
        Yes, the content is dynamic and result comes from an API calls.

        To be honest, I didn’t confirm with them If having text annotation in Russian language would also be a problem, because there were some issue with test account during first plugin review, so they didn’t get a chance to see it. I thought of It only now, writing my question, because If there is a problem for error text, It should be the same for annotations text. I probably overthought it ...gotta check with them.

         

        Because afaik the spelling interfaces you might have tapped will only be triggered and functional when the text language is set to Russian so showing Russian annotations for a Russian text should not be a problem.

         

        Once again, probably overthought myself. But I meant this: if non russian user would like to use the plugin (we gonna skip the part where user also would need to register on the russian app, get an API key e t.c.), he should get text description of an annotation in english, even though annotation itself would desribe Russian spelling rules. I hope you get my initial thought, but I agree, It sounds stupid😁 I've got too worried about what else might happen...

        But question about text errors still remains.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices