Several issues with the template regarding the translation/design

This topic has 74 replies, 6 voices, and was last updated 8 years, 10 months ago ago by mleihs

  • Avatar: mleihs
    mleihs
    Participant
    February 2, 2015 at 14:33

    Hi Eva,

    I had to roll back the changes. I will post again once the current content tasks are finished and the latest update is installed again.

    Best regards

    Avatar: Eva
    Eva Kemp
    Support staff
    February 2, 2015 at 14:56

    Hello @mleihs,

    Ok, let us know if further assistance is needed.

    Thank you.
    Regards,
    Eva Kemp.

    Avatar: mleihs
    mleihs
    Participant
    February 18, 2015 at 12:20

    Hi,

    I updated to Legenda 2.6. #38620 is still an issue.

    Would you mind taking a look at it?

    How to deal with the translation issues in the future? Checking/changing the source files after each update is not very practial. Isn’t there a way to handle translations using .mo/.po files only? Why are some parts “hard wired”?

    Best regards

    Please, contact administrator
    for this information.
    Avatar: mleihs
    mleihs
    Participant
    February 19, 2015 at 08:15

    Hi,

    sry for pushing but the site is offline and people can’t work on the content.

    Please instruct how to proceed. Thank you!

    Best regards

    Avatar: Robert Hall
    Robert Hall
    Support staff
    February 19, 2015 at 08:24

    Hello,

    We’ve taken your request into our account.
    At this time the translate is possible using .mo/.po files only.
    What parts you mean? Please provide us with screenshot and links to them.

    Regards,
    Robert Hall.

    Avatar: mleihs
    mleihs
    Participant
    February 19, 2015 at 10:25

    Hi Robert,

    ok, that sounds great.

    The site is currently broken because the changes I was instructed to apply to get the translation working for the portfolio section apparently aren’t compatible with the new version of the theme.

    Please take a look yourself.

    Best regards

    Please, contact administrator
    for this information.
    Avatar: mleihs
    mleihs
    Participant
    February 19, 2015 at 19:26

    Hi,

    I rolled back the changes made to the child theme. What is the best way to extend the customized .mo/.po files so that the portfolio section can be translated that way?

    Thanks for fixing that issue, btw!

    Best regards

    Avatar: mleihs
    mleihs
    Participant
    February 24, 2015 at 12:20

    Hi,

    I rolled back the changes made to the child theme. What is the best way to extend the customized .mo/.po files so that the portfolio section can be translated that way?

    Thanks for fixing that issue, btw!

    How to migrate the .mo/.po files?

    Did I miss something within the upgrade notes?

    Best regards

    Avatar: Eva
    Eva Kemp
    Support staff
    February 24, 2015 at 17:32

    Hello,

    Unfortunately you can’t move these files into the child theme folder.
    They are active only in the parent theme.
    Why do you need to move them? Your .po files won’t be overwritten after the theme update.

    Regards,
    Eva Kemp.

    Avatar: mleihs
    mleihs
    Participant
    February 26, 2015 at 12:55

    Hi Eva,

    Robert wrote:

    At this time the translate is possible using .mo/.po files only.

    So I concluded that there would be changes within the .mo/.po file structure. -> I removed most source changes done via child theme. Those are the open issues:

    Please take a look at [1] (private content):
    – Within the url “portfolio” instead of “autorinnen” gets listed
    – Within the breadcrumbs “projects” instead of “autorinnen” gets listed

    Best regards

    Please, contact administrator
    for this information.
    Avatar: Eva
    Eva Kemp
    Support staff
    February 26, 2015 at 15:47

    Hello,

    You can translate “Projects” in the file legenda/framework/portfolio.php, edit the code 'name' => _x('Projects', 'post type general name'), (line 13) and write your text instead of “Projects”.

    To translate portfolio slug in the link you need edit the file legenda/framework/portfolio.php (line 41) 'rewrite' => array('slug' => 'portfolio') and rename “portfolio” with your translation.

    Thank you.
    Regards,
    Eva Kemp.

    Avatar: mleihs
    mleihs
    Participant
    February 27, 2015 at 12:10

    Hi,

    Robert said it is finally possible to do this using the .mo/.po files.

    Me:

    How to deal with the translation issues in the future? Checking/changing the source files after each update is not very practial. Isn’t there a way to handle translations using .mo/.po files only? Why are some parts “hard wired”?

    Robert:

    We’ve taken your request into our account.
    At this time the translate is possible using .mo/.po files only.

    Now you are telling me something different. What is going on?

    Changing the source for simple translation issues is really bad because you have to take care of the modification with every update.

    You state that your theme is fully translatable. Changing hardwired words in the source code is not what is meant when talking about support for multible languages.

    Please fix this issue asap. This thread is going on for WEEKS now and there is still no solution, or at least explain why it is a good idea to hardwire language in the source code. Maybe I don’t see the advantage of this.

    Best regards

    Avatar: Eva
    Eva Kemp
    Support staff
    February 27, 2015 at 14:22

    Hello @mleihs,

    Please take our apologies for misunderstandings.
    Robert meant you can actually translate theme content in .po file and not slugs.
    Unfortunately to translate slugs you need edit the file I mentioned in the previous post.

    We’re very sorry for the troubles you had to experience.

    Thank you.
    Regards,
    Eva Kemp.

    Avatar: mleihs
    mleihs
    Participant
    February 27, 2015 at 15:00

    Please fix this issue asap. This thread is going on for WEEKS now and there is still no solution, or at least explain why it is a good idea to hardwire language in the source code. Maybe I don’t see the advantage of this.

    So your recommendation for updating is to reimplement that change after every update?

    Does this sound sane to you?

    Avatar: mleihs
    mleihs
    Participant
    March 2, 2015 at 17:28

    ?

    Avatar: Eva
    Eva Kemp
    Support staff
    March 2, 2015 at 18:48

    Hello,

    You can use child theme and copy the files in there. Or you can always keep the file safe and update it after each theme update.
    We’re sorry for such inconveniences.
    We’ll try to fix it in the nearest update.

    Thank you.
    Regards,
    Eva Kemp.

    Avatar: mleihs
    mleihs
    Participant
    March 3, 2015 at 14:11

    Hi Eva,

    thanks. That’s great news. I really appreciate it.

    I applied the recommended changes to portfolio.php @ child theme but it seems the changes are ignored for now.

    Please take a look yourself.

    Best regards

    Avatar: mleihs
    mleihs
    Participant
    March 4, 2015 at 13:24

    Hi Eva,

    the fuzzy translations stopped working. Maybe it has to do with the latest theme update?

    Do I need to retranslate all the .mo/.po files starting with the .de version of the latest download?

    Please take a look at:

    http://imgur.com/ExVAYgO

    vs

    http://imgur.com/frlicn8

    Best regards,

    Please, contact administrator
    for this information.
    Avatar: Eva
    Eva Kemp
    Support staff
    March 4, 2015 at 15:22

    Hello @mleihs,

    We’re looking into this.
    Once there is a result, we’ll let you know.

    Thank you.
    Regards,
    Eva Kemp.

    Avatar: mleihs
    mleihs
    Participant
    March 4, 2015 at 15:39

    Hi Eva,

    thanks for the reply.

    If you tell me that I need to start over using updated .mo/.po files it is fine. I just don’t wanna waste my/your time and get some clear instructions on how to deal with those translation issues. My client kinda ran out of patience during the last week; so I need to solve this during the next days.

    There’s another book shop project in queue once this one is completed. Maybe others will follow. It’s not much money in terms of licensing but I guess everyone apart from the english speaking realm will be happy if the theme is translatable without getting a stomach ulcer.

    Thanks again!

    Best regards,

  • 1 2 3 4
    Viewing 60 results - 41 through 60 (of 74 total)

The issue related to '‘Several issues with the template regarding the translation/design’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.