Need help? Check out our Support site, then


Translations are not applied II

  1. Since previous topic is closed, I'm opening a new one. I can conclude now that method described by Ze is not working. I translated or re-translated more than 300 strings (my estimation) and translation is still not deployed.

    Even if this mechanism works, translators who regularly update translation are in same basket with other who translate several strings per month. For us who translate regularly and have almost whole translation finished, there should be more often deploy, even if there are lower number of strings.

  2. Serbian was last deployed on Jan.,15th (two days ago), and at this moment has 74 strings pending deploy.

    To restate the previous topic's key point:

    To keep it all in context, deploys affect 8 million + blogs, it is simply not feasible or desirable for the stability of everybody's blog to have the process run at much shorter intervals.

    Now, I do understand that exceptional circumstances may require an exceptional deploy, in which case feel free to request it on these forums.

  3. Well, I don't see results of that deploy because strings that are translated (before January, 15th) are not translated in interface, and sr.po file in SVN is still dated to December, 16th.

  4. Ok, could you give me one or two examples? (and also the URL of the repo you're looking at).

    Thanks

  5. Go to profile page. There is a section "Twitter API". All strings from over there are translated. Since you are logged in, check top nav bar, you will see "Follow this blog" even though this is translated too.

    After inspecting now, I'm sure that there wasn't deploy because all strings I checked weren't updated. Maybe you have some problem with scripts. I also noticed in GlotPress that latest strings that were added are not showing on top although they were several days ago.

    I check sr.po in SVN here.

  6. Good call. There was a string making the deploy abort. (This is only for sr by the way). Could you check now? Thanks and sorry for the troubles.

  7. I'll mark this thread 'resolved'. If you see more strange behavior, I'll "unresolve" it, thanks.

  8. Sorry I didn't write reply before but I was offline (and will be again next days, so you'll maybe wait for my response).

    Your deploy on January 18th have been successful, but there are some problems. These are with contextual strings on dashboard and nav menus on edit.php, edit-page,php, users.php etc. Simply, strings are not shown, either translated or untranslated. This started with deploy in December and I thought that new deploy will solve this but it didn't.

    I don't know reason for this so could you please check it?

    I already reported this in my previous message here, but there is some problem with GlotPress because latest strings are not shown though they are in POT file and when imported in GP via PO/MO they are after that in deployed files.

    There was a string making the deploy abort. (This is only for sr by the way).

    What string is that?

    Thank you for your help.

  9. We're still looking into it, but the culprit seems to be plural forms. A patch has been submitted to the GlotPress trac (see: http://trac.glotpress.org/ticket/59). We'll know more once the patch is analyzed and applied. Thanks and sorry for the troubles.

  10. miladin:

    For us who translate regularly and have almost whole translation finished, there should be more often deploy, even if there are lower number of strings.

    vanillalounge:

    To keep it all in context, deploys affect 8 million + blogs, it is simply not feasible or desirable for the stability of everybody's blog to have the process run at much shorter intervals.

    I agree with miladin. The deployment period should be shortened somehow. My suggestion:

    every 72 hours (or maybe every week):
    if there is a deployment request by a validator, or if there are enough new strings:
    deploy

    (every language has a deployment request flag and after deployment, the flag is removed)

    Also, the last deployment date should be mentioned somewhere in the platform. And it'll be very nice to have newly added strings, which are not yet deployed, in a different color.

  11. every 72 hours (or maybe every week):
    if there is a deployment request by a validator, or if there are enough new strings:
    deploy

    This works for me, as long as we keep in mind that "enough" strings still is around 200. Deploy requests can safely be posted on this forum.

    (every language has a deployment request flag and after deployment, the flag is removed)

    Also, the last deployment date should be mentioned somewhere in the platform.

    We already have that info, I'll see if we can make it visible

    And it'll be very nice to have newly added strings, which are not yet deployed, in a different color.

    The trouble here is the logic, i.e. when does a string cease to be "new" and change back to the normal (non) color? Strings are added practically everyday...

    Furthermore the biggest hurdle right now is not really deploying but much more validating... I see languages with 700+ strings pending validation (the extreme cases)

  12. If you add the date, could you also add the number of string that are remained until next deploy? So we can decide if adding a few more string will activate the deployment or we should request it here in the forums?

    The trouble here is the logic, i.e. when does a string cease to be "new" and change back to the normal (non) color? Strings are added practically everyday...

    I thought you could find that by comparing dates. But I understand if there are some technical difficulties with it.

Topic Closed

This topic has been closed to new replies.

About this Topic