Skip to main content
On the backlog

Handle translations Case Sensitive

Related products:Software Factory
  • July 6, 2022
  • 4 replies
  • 123 views
C. Lousberg
Captain
Forum|alt.badge.img+4

The SF/IAM databases are Case insensitve (Latin1_General_CI_AS) by default.

As we sometimes make some mistakes (who doesn't), we'd like to correct the cases in translations.

E.g. cange “Purchase order” to “Purchase Order”.

 

Currently there are 2 workarounds:

  • update the records in transl table
  • or, change to “Purchase Order1”, sync to all IAM's and change to correct “Purchase Order”

 

The idea we'd like to see implemented is that a collate Latin1_General_CS_AS compare takes place and also the update will take place in this collation so the correct cases will be stored.

    4 replies

    Mark Jongeling
    Administrator
    Forum|alt.badge.img+23
    Updated idea statusNew→Open
    "Wake me up before you low-code"
    Marius Korff
    Jeroen van den Belt
    Administrator
    Forum|alt.badge.img+10
    Open→On the backlog (research phase)
    Marius Korff
    B
    Warrior
    Forum|alt.badge.img+4
    • BramGWarrior
    • Warrior
    • July 10, 2025

    The annoying part is, when you would do a workaround in a development branche and would sync it to a target branche, the merge session will NOT see the conflict and not update the translation in your target branche. 

    Marius Korff
    T
    Ionut
    D
    Rookie
    Forum|alt.badge.img
    • David BRookie
    • Rookie
    • August 6, 2025

    If your phrase contains 2 words, you can add a double space between them “Production  Order” (but not at the end, those are trimmed). This you can let propagate through the merges to your acceptance and production branches. It is barely noticeable in the GUI.

    UPDATE:

    You can add a character that is invisible to humans but visible to the database, at the end of your translation. E.g. copy-paste the character that is between the brackets below:

    [​] ← This contains U+200B

     

    J
    Terms & ConditionsCookie settingsAccessibility statement