Writing helper string

  • Author
  • #1388851


    The “writing helper” metabox in the editor says “Use an existing page|post as a template.


    The term post or page is filled in as a variable. The question is where do the terms “post” and “page” come from within GlotPress? I’m asking because in the german translation the terms “page” and “post” should be capitalized as “Seite” (page) and “Beitrag” (post). But they aren’t.

    In german it reads:
    Verwende eine(n) existierende(n) artikel als Vorlage.
    Verwende eine(n) existierende(n) seite als Vorlage.

    I can’t seem to find the not-capitalized strings “artikel” and “seite” in glotpress.

    While we’re at it, this is another of this variable problems just like in the Reader subscription page string topic.

    In german the term “page” has a female gender (die Seite) while “post” has a male gender (der Beitrag). So while english just uses one sentence “Use an existing %s as a template.” and just fills the variable, german would require two different strings for each gender.

    Verwende einen existierenden Beitrag als Vorlage.
    Verwende eine existierende Seite als Vorlage.

    That’s why we have to work around the problem in the german translation by adding these “(n)” things to catch the gender problem.


    The blog I need help with is iqatrophie.wordpress.com.



    Hi Martin! Thanks for pointing out this issue. :) I reported this to the team, to see if we can produce two separate strings for translation purposes, rather than using a variable. I’ll let you know what I find out!



    Thanks Rachel. :)



    Hi Martin,

    Good news! We were able to add two strings for the sentences you mentioned:

    “Use an existing page as a template.” (DE translation)

    “Use an existing post as a template.” (DE translation)

    There is also now a third, untranslated string, “Use an existing %s as a template.” The variable here comes from the post type label. This string is included because the writing helper is meant to be extendable, so it can handle additional, custom post types by inserting the post type label there. However, we’ll use the two translations above for posts and pages in particular.



    Hi Rachel,

    that’s good news. Thanks for hanging on to it and coming up with a solution. That’ll improve the translation quality. :)

    Could you give me an example sentence with a post type label? What kind of strings will the variable hold? Will it be something like

    Use an existing aside|quote|link|… as a template


    If this is the case, we might have jumped from the frying pan into the fire because “aside” has a female gender (die Kurzmitteilung), “link” has a male gender (der Link) and “quote” even has a neuter gender (das Zitat). Due to the neuter gender, translating this string correctly is nearly impossible. See the following examples:

    • Verwende eine vorhandene Kurzmitteilung als Vorlage.
    • Verwende einen vorhandenen Link als Vorlage.
    • Verwende ein vorhandenes Zitat als Vorlage.
    • This would leave us with a translation like

      Verwende ein(e|en) vorhanden(e|en|es) %s als Vorlage.



    Unfortunately, the translation you proposed for the third string may be necessary here:

    Verwende ein(e|en) vorhanden(e|en|es) %s als Vorlage.

    The three terms you mentioned (aside, quote, and link) are actually post formats, rather than post types, but you’re right that we may have to account for all three genders in this sentence. Here is what the WordPress Codex says about post types: http://codex.wordpress.org/Post_Types

    The five default post types are post, page, attachment, revision, and navigation menu. However, custom post types could be created with any name (and thus any gender when translated). Thankfully, the two most common cases (post and page) will use the specific strings we just created.



    Hi Rachel,

    thanks for clarifying the term “post type”. It seems my proposed translation is the only solution but I have to admit it reads horrible. ;)

The topic ‘Writing helper string’ is closed to new replies.