To be translation ready, all "hard-coded" text strings that are outputted to the screen should be properly addressed under the i18n guidelines.<br>This includes both the "public-facing" (read: text seen by the reader); and, possibly more important, the text seen by writer so they are provided the information on each feature / function they are using when writing and publishing their posts, etc.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Thu, Sep 13, 2012 at 7:56 AM, Lmm Muc <span dir="ltr"><<a href="mailto:lmmmuc@gmail.com" target="_blank">lmmmuc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On the subject of translating front-end and/or back-end of a theme: <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2012-September/010664.html" target="_blank">http://lists.wordpress.org/<u></u>pipermail/theme-reviewers/<u></u>2012-September/010664.html</a><br>
<br>
"Public-facing" seems pretty clear to me, both semantically and in the context it is being used in the Review Guidelines ("public-facing credit link"). It obviously means the text on the front end of a web site, the part that faces "the public", with the public being the visitors of a site. It would be a stretch to count the back end of a theme as "facing the public" - in this context.<br>
<br>
The amount of text in a theme back end can be huge, even more so if a lot of additional usage information is provided. It would be an undue burden for translators if they had to translate that as well in order to create a full translation of a theme. What about illustrational graphics in the back end? If we wanted to be really pedantic there would also have to be localized versions of graphics that contain text. Back end text may also change more frequently than text on the the front end.<br>
<br>
This should be clarified in the review guidelines. A theme should count as being "translation-ready" if all public-facing text is localized, with "public facing" being all the text that appears or may appear on the front end of a site.<br>
<br>
It shouldn't be mandatory to have the back end localized as well. Perhaps there should be a second theme tag for this?<br>
<br>
Greetings<br>
Flynn<br>
<br>
<br>
On 11.09.2012 04:58, <a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.<u></u>wordpress.org</a> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send theme-reviewers mailing list submissions to<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.<u></u>wordpress.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:theme-reviewers-owner@lists.wordpress.org" target="_blank">theme-reviewers-owner@lists.<u></u>wordpress.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of theme-reviewers digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Translation Support (Vicky Arulsingam)<br>
2. Re: Translation Support (Bryan Hadaway)<br>
3. Re: Translation Support (Emil Uzelac)<br>
4. Re: Translation Support (Vicky Arulsingam)<br>
5. Re: Translation Support (Emil Uzelac)<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>----------<br>
<br>
Message: 1<br>
Date: Tue, 11 Sep 2012 09:38:00 +0800<br>
From: Vicky Arulsingam <<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>><br>
Subject: [theme-reviewers] Translation Support<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
Message-ID:<br>
<CALc3iY0uN1k=<u></u>YTvduK7x2zwj0RmXGW6=<a href="mailto:BESJY1CSng-R_abVyw@mail.gmail.com" target="_blank">BESJY1CSng<u></u>-R_abVyw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
There seems to be some confusion regarding this item in the Theme Review<br>
guidelines in one of the reviews I'm doing with regards to Translation<br>
Support.<br>
<br>
"Themes are *required* to have all public-facing text in English."<br>
<br>
My understanding is that all text the user sees - on the front-end (viewing<br>
the site) and the back-end (admin pages) must be localized.<br>
Others feel that this only refers to the front-end.<br>
<br>
I personally find it strange that you're not going to translate theme<br>
options so a clarification would be great.<br>
<br>
Or perhaps a better discussion would be: in what cases would there be an<br>
exception to translation e.g. dummy text in special templates?<br>
<br>
Thanks<br>
-----<br>
Vicky Arulsingam<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120911/dec8b940/attachment-0001.htm" target="_blank">http://lists.wordpress.org/<u></u>pipermail/theme-reviewers/<u></u>attachments/20120911/dec8b940/<u></u>attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 10 Sep 2012 19:41:26 -0600<br>
From: Bryan Hadaway <<a href="mailto:bhadaway@gmail.com" target="_blank">bhadaway@gmail.com</a>><br>
Subject: Re: [theme-reviewers] Translation Support<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
Message-ID:<br>
<CAP3jXhR=MzAS_G7RKBc-<u></u>PbGQUtNWOLTu9SqXuyhShWsh=<a href="mailto:gikHQ@mail.gmail.com" target="_blank">gikHQ<u></u>@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I think so, I'd wait for an admin of course. A good appendage also would be<br>
"*by default*".<br>
<br>
So something like:<br>
<br>
*Themes are required to have all public-facing (both the front-end and<br>
back-end) text in English by default.*<br>
<br>
<br>
Bryan Phillip Hadaway<br>
<br>
<br>
Web & Graphic Designer<br>
<a href="http://calmestghost.com" target="_blank">calmestghost.com</a><br>
<a href="mailto:bhadaway@gmail.com" target="_blank">bhadaway@gmail.com</a><br>
<br>
<br>
*Socialize:* Facebook <<a href="http://www.facebook.com/calmestghost" target="_blank">http://www.facebook.com/<u></u>calmestghost</a>> |<br>
Twitter<<a href="http://twitter.com/calmestghost" target="_blank">http://twitter.com/<u></u>calmestghost</a>> |<br>
LinkedIn <<a href="http://www.linkedin.com/in/calmestghost" target="_blank">http://www.linkedin.com/in/<u></u>calmestghost</a>> |<br>
Google+<<a href="https://plus.google.com/104582075016689917593" target="_blank">https://plus.google.<u></u>com/104582075016689917593</a>><br>
<br>
<br>
<br>
On Mon, Sep 10, 2012 at 7:38 PM, Vicky Arulsingam <<br>
<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There seems to be some confusion regarding this item in the Theme Review<br>
guidelines in one of the reviews I'm doing with regards to Translation<br>
Support.<br>
<br>
"Themes are *required* to have all public-facing text in English."<br>
<br>
My understanding is that all text the user sees - on the front-end<br>
(viewing the site) and the back-end (admin pages) must be localized.<br>
Others feel that this only refers to the front-end.<br>
<br>
I personally find it strange that you're not going to translate theme<br>
options so a clarification would be great.<br>
<br>
Or perhaps a better discussion would be: in what cases would there be an<br>
exception to translation e.g. dummy text in special templates?<br>
<br>
Thanks<br>
-----<br>
Vicky Arulsingam<br>
<br>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
<br>
<br>
</blockquote>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120910/acabe1b3/attachment-0001.htm" target="_blank">http://lists.wordpress.org/<u></u>pipermail/theme-reviewers/<u></u>attachments/20120910/acabe1b3/<u></u>attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 10 Sep 2012 21:34:18 -0500<br>
From: Emil Uzelac <<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>><br>
Subject: Re: [theme-reviewers] Translation Support<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
Message-ID:<br>
<<a href="mailto:CAG4s18iMsRGtU6TmDNhDC3hZdpPCFSr00Vi95P9O43CJBnBFTA@mail.gmail.com" target="_blank">CAG4s18iMsRGtU6TmDNhDC3hZdpPC<u></u>FSr00Vi95P9O43CJBnBFTA@mail.<u></u>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
This is actually pretty straightforward (IMO).<br>
<br>
Public-facing: *Theme Created by Author* (front-end) *Theme Options... etc..<br>
* (back-end) examples only.<br>
<br>
So if author is including e.g. Theme Options, all that should be in English<br>
too, but also everything else visible to the user.<br>
<br>
Localization in this case is not a requirement :)<br>
<br>
Thanks,<br>
Emil<br>
<br>
On Mon, Sep 10, 2012 at 8:41 PM, Bryan Hadaway <<a href="mailto:bhadaway@gmail.com" target="_blank">bhadaway@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think so, I'd wait for an admin of course. A good appendage also would<br>
be "*by default*".<br>
<br>
So something like:<br>
<br>
*Themes are required to have all public-facing (both the front-end and<br>
back-end) text in English by default.*<br>
<br>
<br>
Bryan Phillip Hadaway<br>
<br>
<br>
Web & Graphic Designer<br>
<a href="http://calmestghost.com" target="_blank">calmestghost.com</a><br>
<a href="mailto:bhadaway@gmail.com" target="_blank">bhadaway@gmail.com</a><br>
<br>
<br>
*Socialize:* Facebook <<a href="http://www.facebook.com/calmestghost" target="_blank">http://www.facebook.com/<u></u>calmestghost</a>> | Twitter<<a href="http://twitter.com/calmestghost" target="_blank">http://twitter.com/<u></u>calmestghost</a>> |<br>
LinkedIn <<a href="http://www.linkedin.com/in/calmestghost" target="_blank">http://www.linkedin.com/in/<u></u>calmestghost</a>> | Google+<<a href="https://plus.google.com/104582075016689917593" target="_blank">https://plus.google.<u></u>com/104582075016689917593</a>><br>
<br>
<br>
<br>
On Mon, Sep 10, 2012 at 7:38 PM, Vicky Arulsingam <<br>
<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There seems to be some confusion regarding this item in the Theme Review<br>
guidelines in one of the reviews I'm doing with regards to Translation<br>
Support.<br>
<br>
"Themes are *required* to have all public-facing text in English."<br>
<br>
My understanding is that all text the user sees - on the front-end<br>
(viewing the site) and the back-end (admin pages) must be localized.<br>
Others feel that this only refers to the front-end.<br>
<br>
I personally find it strange that you're not going to translate theme<br>
options so a clarification would be great.<br>
<br>
Or perhaps a better discussion would be: in what cases would there be an<br>
exception to translation e.g. dummy text in special templates?<br>
<br>
Thanks<br>
-----<br>
Vicky Arulsingam<br>
<br>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
<br>
<br>
</blockquote>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120910/de2db8b7/attachment-0001.htm" target="_blank">http://lists.wordpress.org/<u></u>pipermail/theme-reviewers/<u></u>attachments/20120910/de2db8b7/<u></u>attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 11 Sep 2012 10:47:48 +0800<br>
From: Vicky Arulsingam <<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>><br>
Subject: Re: [theme-reviewers] Translation Support<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
Message-ID:<br>
<CALc3iY2bs+zMRnyNqfsfOTnhhr+<u></u>rnH5qK8=<a href="mailto:n0WzAObpXpBdH-A@mail.gmail.com" target="_blank">n0WzAObpXpBdH-A@mail.<u></u>gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I agree with you - "Public facing" = "Everything the user sees"<br>
<br>
I understand that localization is optional. The situation is the theme<br>
author is supporting translation but he has only localized the template<br>
files because he understands that "Public-Facing" is just the front-end.<br>
The theme options haven't been localized.<br>
<br>
I just wanted to make sure that everyone here has the same understanding :)<br>
<br>
Thanks<br>
-----<br>
Vicky Arulsingam<br>
<br>
<br>
On Tue, Sep 11, 2012 at 10:34 AM, Emil Uzelac <<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is actually pretty straightforward (IMO).<br>
<br>
Public-facing: *Theme Created by Author* (front-end) *Theme Options...<br>
etc..* (back-end) examples only.<br>
<br>
So if author is including e.g. Theme Options, all that should be in<br>
English too, but also everything else visible to the user.<br>
<br>
Localization in this case is not a requirement :)<br>
<br>
Thanks,<br>
Emil<br>
<br>
<br>
</blockquote>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120911/882e847c/attachment-0001.htm" target="_blank">http://lists.wordpress.org/<u></u>pipermail/theme-reviewers/<u></u>attachments/20120911/882e847c/<u></u>attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 10 Sep 2012 21:58:09 -0500<br>
From: Emil Uzelac <<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>><br>
Subject: Re: [theme-reviewers] Translation Support<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
Message-ID:<br>
<<a href="mailto:CAG4s18gfSmVvbEADDE7t1c14DVpQu4dHCEJBFRUbuY7ttbrrwQ@mail.gmail.com" target="_blank">CAG4s18gfSmVvbEADDE7t1c14DVpQ<u></u>u4dHCEJBFRUbuY7ttbrrwQ@mail.<u></u>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
it's all good :)<br>
<br>
Emil<br>
<br>
On Mon, Sep 10, 2012 at 9:47 PM, Vicky Arulsingam <<br>
<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I agree with you - "Public facing" = "Everything the user sees"<br>
<br>
I understand that localization is optional. The situation is the theme<br>
author is supporting translation but he has only localized the template<br>
files because he understands that "Public-Facing" is just the front-end.<br>
The theme options haven't been localized.<br>
<br>
I just wanted to make sure that everyone here has the same understanding :)<br>
<br>
Thanks<br>
-----<br>
Vicky Arulsingam<br>
<br>
<br>
On Tue, Sep 11, 2012 at 10:34 AM, Emil Uzelac <<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is actually pretty straightforward (IMO).<br>
<br>
Public-facing: *Theme Created by Author* (front-end) *Theme Options...<br>
etc..* (back-end) examples only.<br>
<br>
So if author is including e.g. Theme Options, all that should be in<br>
English too, but also everything else visible to the user.<br>
<br>
Localization in this case is not a requirement :)<br>
<br>
Thanks,<br>
Emil<br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
<br>
<br>
</blockquote>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120910/af5ffee8/attachment.htm" target="_blank">http://lists.wordpress.org/<u></u>pipermail/theme-reviewers/<u></u>attachments/20120910/af5ffee8/<u></u>attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
<br>
<br>
End of theme-reviewers Digest, Vol 28, Issue 40<br>
******************************<u></u>*****************<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</blockquote></div><br>