Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #112920
    mihailo
    Participant

    Hi,

    My project includes localization in Spanish and Serbian. I have started the translation using the provided .pot. However, the issue I am currently experiencing is that the Read More and Search bar strings are taken from the customization instead of the translation files.

    Admittedly, I had initially changed the default values hoping that they will appear in Polylang’s Strings translations page. Since they didn’t, I went to plan B: creating the translation files. Still the customized values appeared. I tried putting back the default values and removing the strings in customization altogether. Nothing worked.

    Is there a way for me to force the translation strings to be used?

    I should mention that I am using a child theme.

    Many thanks,
    Mihailo

    #112953
    Mahesh
    Keymaster

    @mihailo: Well, its because, there is no translation for Spanish or Serbian language for the theme yet. Have you made the translation file? If yes, please share it here. Let me know further.
    And about translation ready. Pro version are translation ready and is compatible with WPML and Qtranslate-X plugins.

    Regards,
    Mahesh

    #113000
    mihailo
    Participant

    Hi Mahesh,

    Thank you for the very prompt reply.

    I have indeed created the translation files. Only about 5% are done since I didn’t need any more.

    In the end I found a workaround. Using Option Inspector, I removed the following two lines from theme_mods_clean-magazine and theme_mods_clean-magazine_child:

    • ‘excerpt_more_text’ => ‘Read More …’,
    • ‘search_text’ => ‘Search…’,

    After that, the translation strings are properly loading. Probably not the smartest and cleanest way of doing it, though.
    I think it would be great to have the option within the customization to simply specify that translation strings will be used, instead of the values defined in wp_options.

    Thanks again,
    Mihailo

    #113043
    Mahesh
    Keymaster

    @mihailo: It’s better to have 100% translation. And Yes, it woud be really great and simple to have specific translation strings within the customization but that didn’t seem to be working. Please contact the plugins support if they have any solution.

    Regards,
    Mahesh

Viewing 4 posts - 1 through 4 (of 4 total)
  • The topic ‘Read More … and Search… translation strings not being used’ is closed to new replies.