Skip to main content
D
demo_5934
Participating Frequently
August 9, 2025
Question

Lightroom ignores localisation strings in Profile/User Presets

  • August 9, 2025
  • 1 reply
  • 179 views

Version of the app: LrC 14.4 & iOS Lightroom v10.4.2

 

Platform and OS version: Windows 10 & iOS 18.6

 

Basic steps to reproduce the problem

As per the instructions in "Enhanced Profiles" (obtained from ACR_and_Lightroom_Profile_SDK, https://helpx.adobe.com/au/camera-raw/digital-negative.html ), I added the following translated strings to both Profile and User Presets. See the attached User Preset as an example.

   <crs:Name>
    <rdf:Alt>
     <rdf:li xml:lang="x-default">相机标准</rdf:li>
     <rdf:li xml:lang="en">Camera Standard</rdf:li>
    </rdf:Alt>
   </crs:Name>
   <crs:Group>
    <rdf:Alt>
     <rdf:li xml:lang="x-default">测试</rdf:li>
     <rdf:li xml:lang="en">test</rdf:li>
    </rdf:Alt>
   </crs:Group>

 

Expected result

After switch the program language to English, translated strings should be shown.

 

Actual result

Still showing the default strings. Please help to look into this issue. Thanks!

1 reply

johnrellis
johnrellis
Legend
August 9, 2025

Building on this, none of the .xmp presets and enhanced profiles included in LR include translations using "xml:lang". (See /Library/Application Support/Adobe/CameraRaw/Settings.) Instead, the translations are provided in the TranslatedStrings.txt files.

 

So I suspect that the developers will declare this "as designed", and if so, you should ask the moderators to move this to the Ideas section. 

D
demo_5934Author
Participating Frequently
August 9, 2025

Built-in profile/preset is a bad example as they were created and maintained by Adobe. The benifit for TranslatedStrings.txt is it provides a centralised location for Adobe to update trasnlations, instead of updating one file after another.

 

The issue I reported was meant for creating your own profiles/presets. I don't belive it is "as- designed" because they are customized by the creaters and it's out of Adobe's hand. The instruction of creating enhanced profiles was drafted by Adobe as parts of the SDKs. So Lightroom and ACR should follow the same standard/design to be able to show localised strings in profiles/presets genrated by users.

johnrellis
johnrellis
Legend
August 9, 2025

I fully agree that it would be better for LR to implement the xml:lang mechanism as described in the SDK. Rather, I'm trying to explain how Adobe (not me) is likely to view this issue to help you be more successful in getting their attention.

 

Your example .xmp demonstrates that neither LR Classic nor Camera Raw currently implement the full xml:lang mechanism. Given that LR/CR uses the same code to read both built-in and user presets/profiles, and given that LR/CR doesn't rely on the xml:lang mechanism for built-in presets/profiles, I think it's more likely that Adobe never implemented it. I think it's less likely that Adobe implemented it but that something is broken in that part of the code.

 

If it's the case that Adobe does have code that implemented xml:lang but that the code is broken, then they would consider that as a "bug", code that's not working as originally designed by the product manager or engineer. But if Adobe never implemented xml:lang alternatives for presets and profiles, they would probably consider the current behavior "as designed", regardless of what an old document says. (See here for an example of LR's failure to meet the requirements of an industry standard being considered by Adobe "as designed" rather than as a bug.)

 

Your post is currently in the Discussions section of the forum. Did you originally submit it to the Bugs section?  If so, that indicates that Adobe has already decided it doesn't qualify under their definition of "bug".  And in that case, or if it doesn't get moved to Bugs in a few days, it would be a little more likely to get attention from Adobe if you submit it to the Ideas section. Only a small percentage of things in the Ideas section get implemented, but some do.

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