Forum Discussion

wpigoury's avatar
wpigoury
Mentor
12 years ago

French mistype for read-only messages

Hi,

 

There's a mistype for read-only messages.

When you are on a thread in the options and when you have marked a thread as read-only the french translation is false.

It's written "vérouillé" it should be "verrouillé".

 

With the toolbelt I was able to override the text in the options but I couldn't find the string for the text inside the message (see capture).

 

Could you please correct it and in the meantime help me find the string to override ?

 

Thanks.


cap.png

6 Replies

  • PaoloT's avatar
    PaoloT
    Lithium Alumni (Retired)
    12 years ago

    Hi wpigoury,

     

    if you can't find the string using the toolbelt or the Studio Text Editor - then it may be that it is coming from a customization and it may have been hardcoded in a custom component. If you are unable to find it - I suggest raising a support ticket so that our engineers can have a closer look at the problem.

     

    Hope this helps

  • JohnD's avatar
    JohnD
    Khoros Alumni (Retired)
    12 years ago
    I did a search for this string in our french text properties file and couldn't find a match. I think that your suspicion that this string is in a custom component is correct.
  • wpigoury's avatar
    wpigoury
    Mentor
    12 years ago

    We have this text neither in our custom components or in our other customizations (string or even js).

    And it was mistyped in the options menu which we hadn't modified at the time.

    So I'm pretty sure it comes from the default translation but I will open a support ticket to make sure.

     

    Thanks.

  • Nariman's avatar
    Nariman
    Lithium Alumni (Retired)
    12 years ago
    Hi wpigoury
    Can you provide steps to reproduce this?
  • wpigoury's avatar
    wpigoury
    Mentor
    12 years ago

    My bad, it was indeed in a custom component I was not aware of.

    I don't understand why I couldn't find the string when searching accros our repository but the support pointed it out for us.

     

    Sorry to have bother you.

  • PaoloT's avatar
    PaoloT
    Lithium Alumni (Retired)
    12 years ago

    Hi wpigoury,

     

    the Studio Text search looks up at the key / values pair that are defined in the platform. If a component is using hardcoded text - then the tool will not be able to find that. 

     

    If you need the ability of controlling the text in the custom components via the text editor, you can always build custom components that are using the text freemarker context object and create a custom text key that you can then render within the component as suggested in the example TKB article. In this way, you won't have hardcoded text in the customizations.

     

    Hope this helps,