Possible error in fuzzy string
-
I’ve come across a fuzzy string in GlotPress and I’m not sure if about it.
%1$s and %2$s followed your blog %2$s
The string uses the variable “%2$s” in two places. Is this right? As far as I understand the string, the first two variables should be usernames while the last one appears to be a blog title. In that case the last variable should be “%3$s”. Am I right?
Gruß
Martin(IQ)The blog I need help with is: (visible only to logged in users)
-
The string uses the variable “%2$s” in two places. Is this right? As far as I understand the string, the first two variables should be usernames while the last one appears to be a blog title. In that case the last variable should be “%3$s”. Am I right?
Yes that is correct. It will replace the respective username and site.
Cheers!
-
Hi Grace,
thanks for answering. Maybe I didn’t describe the problem correctly, but wouldn’t the current english (original) string – due to using “%2$s” in two places – look like the following after substitution?
USER1 and USER2 followed your blog USER2
-
-
I came across the string because I’m a validator for german on translate.wordpress.com and this is one of the new fuzzy strings. I’ve linked to the string in my first post.
I reported it because I have a suspicion the original string might be wrong. I’m not talking about the current german translation or the fact that it’s a fuzzy string. I’m wondering why the string uses the second variable in two places. Shouldn’t the last variable be “%3$s” instead?
The comment in the .po file for this string reads:
public.api/rest/wpcom-json-endpoints/class.wpcom-json-api-notes-v2-0-endpoint.php:354
-
In a similar string (see below), the last variable is numbered correctly.
-
Hi there,
Thanks for this! I have reported this to our team for review. I’ll update as soon as I hear back!
Cheers!
-
Hi there!
Our developer has fixed it and it should be updated on GlotPress soon! Thanks for the help!
Cheers!
-
Hi Grace,
thanks for reporting and fixing. Glad I could help prevent some possible support tickets. :) I marked the topic as “resolved” now.
Cheers
Martin -
- The topic ‘Possible error in fuzzy string’ is closed to new replies.