• Hi,
    Just started translating this nice plugin to Swedish.
    I’ve stumbled upon some strings that make life a bit harder for translators.

    See https://plugins.trac.wordpress.org/browser/autodescription/trunk/inc/classes/doing-it-right.class.php around line 1277

    /* translators: 1 = But or And, 1 = Post/Page  */
    $ind_notice .= '<br>' . sprintf( \esc_attr__( '%1$s this %2$s is in draft; therefore, indexing has been discouraged.', 'autodescription' ), $but_and, $args['post_i18n'] );

    1. I guess you’re trying to build a nice language by selecting “But” or “And” based on some rules. However: I’d need to dive deeply into the code to figure out how you’re actually doing that. And intuitively I feel that one shouldn’t take for granted that “But” and “And” always are handled the same way.
    Quite often I notice that I get much better flow in translations to Swedish if I’m not forced to use the words “and”/”or” as fixed terms.

    2. %2$s can be the word page or the word post.
    “This Page” will in Swedish become “Denna sida”, and “This Post” will become “Detta inlägg”. As you can see, the noun steers different form of the word “This”.
    There are more strings with the same problem, for example: “Bots are discouraged to archive this %s.”

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Hi Tor-Bjorn,

    Thank you so much for translating! 🙂 It’s great that you’re actively considering the context of the translations.

    1) Yes, that’s exactly what I was trying to do. And yes, it is a burden on translators. For that, I recently opened an issue with a suggestion to tackle that: https://github.com/sybrew/the-seo-framework/issues/415

    This will probably be resolved as early as v3.4.0, and I may push it to v3.3.0.

    2) And yes, you’re right! I’ve discussed this recently with the Polyglots at Slack, and I summarized necessary changes for this, too: https://github.com/sybrew/the-seo-framework/issues/414

    Most of these changes are planned for v3.3.0.

    I think we’re very much on the same line on this one 😀 Neither of the suggested improvements is set in stone; so, if you have better suggestions, feel free to share them!

    Great. I commented on those two issues.
    You may also want to look at how you handle “here”, “this”, where it looks as if you’re linking to more information, and you replace the linked word and the link with a parameter. Better to use to placeable parameters for the html tags but make the complete sentence translatable, something like:
    “You can read more about this function in the %1$shandbook%2$s.” 1. link to handbook, 2. link end tag

    (Perhaps you’ve already got an issue for this, as well. 🙂

    Hmm. I’ve got a feeling that I somehow were involved in that discussion. Heh. Thanks for caring!

    Plugin Author Sybre Waaijer

    (@cybr)

    Yes, I want to handle all strings with links via Markdown:

    markdown_function( sprintf( __( 'You can find the sitemap [here](%s)' ), $link ) )
    

    (where $link may or may not need translating, too)

    Not all translators are aware of how Markdown works, but I go over the translations now and then to correct mistakes.

    And you were 🙂 You pointed me to the German style guide. I linked to the archive at issue 414.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Some notes from a translator’ is closed to new replies.