Title: request &#8211; unique translation string
Last modified: January 15, 2023

---

# request – unique translation string

 *  Resolved [Johannes Jülg](https://wordpress.org/support/users/timse201/)
 * (@timse201)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/request-86/)
 * Hello,
 * many languages have variations of articles:
 * [https://en.wikipedia.org/wiki/Article_(grammar)#Crosslinguistic_variation](https://en.wikipedia.org/wiki/Article_(grammar)#Crosslinguistic_variation)
 * For german users, the following string is translated as follows:
 * [https://translate.wordpress.org/projects/wp-plugins/autodescription/stable/de/formal/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=1426119&filters%5Btranslation_id%5D=95579107](https://translate.wordpress.org/projects/wp-plugins/autodescription/stable/de/formal/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=1426119&filters%5Btranslation_id%5D=95579107)
 * Could you please make a unique string for these two translations.
    -  This topic was modified 3 years, 4 months ago by [Johannes Jülg](https://wordpress.org/support/users/timse201/).

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

 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/request-86/#post-16383431)
 * Hi Johannes,
 * Thank you for translating!
 * Isn’t it possible to omit articles in some form, like this: `%s SEO-Einstellungen`?
 * I translated the plugin into Dutch and faced the same “die” (der) and “dat” (
   das) issues. If you hit the “Other Languages” tab under the translation entry,
   you can find my Dutch translations, where I took liberties reconstructing sentences
   to avoid articles. Maybe those can aid you 🙂
 * This article exception isn’t listed, but it’s still good to keep handy: [https://de.wordpress.org/mitwirken/style-guide-fuer-uebersetzungen/](https://de.wordpress.org/mitwirken/style-guide-fuer-uebersetzungen/).
 *  Thread Starter [Johannes Jülg](https://wordpress.org/support/users/timse201/)
 * (@timse201)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/request-86/#post-16404880)
 * unfortunately this is also not 100% correct.
 * It should be “Seite**n**-SEO-Einstellungen”, “Beitrag**s**-SEO-Einstellungen”(
   missing letter highlighted)
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/request-86/#post-16405181)
 * We cannot programmatically determine which article should be used, for there 
   are no linguistic rules determining the gender of a noun (other than learning
   them by heart). Since any post type can be used (think of Products for WooCommerce,
   or Events for calendar software), this must remain a placeholder. Of course, 
   we could plainly make it “SEO-Einstellungen,” but that’s boring.
 * For Finish, the translators used `SEO-asetukset (%s)` (i.e., `SEO-Einstellungen(%
   s)`). I’m not a fan of this.
 * The Swedish translators used `SEO-inställningar för %s` (i.e., `SEO-Einstellungen
   für %s`). I think that would be the best one: simply omitting the article. Post,
   Page, Product, and many others are names for the post types, after all.
 *  Thread Starter [Johannes Jülg](https://wordpress.org/support/users/timse201/)
 * (@timse201)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/request-86/#post-16405624)
 * Unfortunately this is not grammatically correct either. I’m sorry.
 * I don’t think this only affects the german language.
 * How about some logic, so we cover the standard WordPress post types and each 
   individual post type will get the placeholder? That way most of your users will
   get a 100% correct translation.
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/request-86/#post-16408265)
 * Hi Johannes,
 * I either do it right for everything and everyone or not do it at all.
 * Have you considered that Seite, Produkt, and Beitrag are proper nouns (names)
   instead of common nouns (objects)? Like this: “SEO-Einstellungen für Sybre” —
   is that grammatically correct? If so, we could consider `%s` a proper noun and
   have it be a little quirky.
 * Still, I believe you can omit articles for common nouns in titles/names/buttons
   regardless, as is the case in most Western Germanic languages (including Dutch
   and English) — the string in question is a title of a meta box. It might not 
   look right or form a perfect sentence, but it’s better than listing all possible
   articles.
 * If you are confident it isn’t possible to work around this issue, I’ll have to
   remove the placeholder so that it becomes simply “SEO-Einstellungen” and “Startseiten-
   SEO-Einstellungen”. No harm done, and it might even work better on smaller screens.
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/request-86/#post-16459280)
 * I’m going to remove the `%s` in the next update — it’ll just be “SEO Settings”.
   This will also help us migrate TSF into Gutenberg’s ridiculously tiny sidebar.

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

The topic ‘request – unique translation string’ is closed to new replies.

 * ![](https://ps.w.org/autodescription/assets/icon.svg?rev=3000376)
 * [The SEO Framework – Fast, Automated, Effortless.](https://wordpress.org/plugins/autodescription/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autodescription/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autodescription/)
 * [Active Topics](https://wordpress.org/support/plugin/autodescription/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autodescription/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autodescription/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/request-86/#post-16459280)
 * Status: resolved