You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Michael Wechner <mi...@wyona.com> on 2005/06/11 13:24:29 UTC
untranslated problem
Hi
I still receive from time to time "untranslated" on i18n stuff and it's not
clear to me what the reason for this is. Any other people experiencing this?
Thanks
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by Michael Wechner <mi...@wyona.com>.
solprovider@gmail.com wrote:
>
>The nice thing about Domino is I can easily convert the output any way
>you want. So what do you want?
>
>
xdoc would be great
Michi
>solprovider
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>For additional commands, e-mail: dev-help@lenya.apache.org
>
>
>
>
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
solprovider@gmail.com wrote:
> On 6/11/05, Gregor J. Rothfuss <gr...@apache.org> wrote:
>
>>heh. agreed. now if only they were not such horrible markup and
>>therefore easier to transfer to lenya.apache.org :)
> The nice thing about Domino is I can easily convert the output any way
> you want. So what do you want?
i usually run your articles through tidy to convert them to xhtml, and
then start working on them in forrest, replacing <br> with <p> etc.
it's a lot of work for every page, so having this cleaned up in lenya
would help a lot.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by so...@gmail.com.
On 6/11/05, Gregor J. Rothfuss <gr...@apache.org> wrote:
> heh. agreed. now if only they were not such horrible markup and
> therefore easier to transfer to lenya.apache.org :)
I almost added a note asking if you wanted this for the official site,
but figured you would notice it.
I am using Domino for the datastore, but I am typing most of it. I
learned HTML before the P tag became popular, and still prefer <BR>.
(I did add a tool to add/remove the <BR>s and convert the angle
brackets between "normal" and "HTML" modes. I hate extra typing.) I
may convert it to Lenya if I ever get mod_proxy_html working.
The nice thing about Domino is I can easily convert the output any way
you want. So what do you want?
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Michael Wohlfart wrote:
> <i18n:text i18n:key="key_text">Default value</i18n:text>
>
> The string "Default value" is displayed if "key_text" isn't
> found in the dictionary
>
> pros:
> 1. The text reads correctly (if you ignore the key)
> 2. Maintenance is easy in the dictionaries
+1 this is how it should be done
> BTW: Thanks for your articles, they really helped me a lot to get
> started with Lenya.
heh. agreed. now if only they were not such horrible markup and
therefore easier to transfer to lenya.apache.org :)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re[2]: untranslated problem
Posted by qMax <qm...@mediasoft.ru>.
Sunday, June 12, 2005, 2:17:37 AM, Michael Wohlfart wrote:
MW> <i18n:text i18n:key="key_text">Default value</i18n:text>
MW> The string "Default value" is displayed if "key_text" isn't
MW> found in the dictionary
MW> pros:
MW> 1. The text reads correctly (if you ignore the key)
MW> 2. Maintenance is easy in the dictionaries
3. having (contexted!) keys also allows more quality translations for words appeared
in various contexts.
MW> The only drawback is that you don't get a friendly "untranslated"
MW> warning if you forget to translate a key.
For native speaking translators it's not much hard to note foreign phrase in a page.
And IMHO, keeping translations in sync (avoiding missing keys) is issue of maitaining
dictionaries, rather then debugging pages.
I posted some suggestions about it at
"Translation catalogues synchronization.":
http://thread.gmane.org/gmane.comp.cms.lenya.user/6965
--
qMax
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by so...@gmail.com.
On 6/11/05, Michael Wohlfart <mi...@zsw-bw.de> wrote:
> nice Article,
> BTW: Thanks for your articles, they really helped me a lot to get
> started with Lenya.
You are welcome.
> a link to the cocoon docs about the i18n transformer would also
> be nice:
> http://cocoon.apache.org/2.1/userdocs/transformers/i18n-transformer.html
Link added.
> you just missed my preferred way to implement i18n ;-)
> <i18n:text i18n:key="key_text">Default value</i18n:text>
> The string "Default value" is displayed if "key_text" isn't
> found in the dictionary
> pros:
> 1. The text reads correctly (if you ignore the key)
> 2. Maintenance is easy in the dictionaries
> The only drawback is that you don't get a friendly "untranslated"
> warning if you forget to translate a key.
I added this option, expanded to remove the "drawback". Enjoy.
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by Michael Wohlfart <mi...@zsw-bw.de>.
nice Article,
you just missed my preferred way to implement i18n ;-)
<i18n:text i18n:key="key_text">Default value</i18n:text>
The string "Default value" is displayed if "key_text" isn't
found in the dictionary
pros:
1. The text reads correctly (if you ignore the key)
2. Maintenance is easy in the dictionaries
The only drawback is that you don't get a friendly "untranslated"
warning if you forget to translate a key.
a link to the cocoon docs about the i18n transformer would also
be nice:
http://cocoon.apache.org/2.1/userdocs/transformers/i18n-transformer.html
BTW: Thanks for your articles, they really helped me a lot to get
started with Lenya.
Michael
solprovider@gmail.com wrote:
> Just created:
> http://solprovider.com/lenya/i18n
>
> Corrections? Suggestions?
>
> solprovider
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by so...@gmail.com.
Just created:
http://solprovider.com/lenya/i18n
Corrections? Suggestions?
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: untranslated problem
Posted by so...@gmail.com.
On 6/11/05, Michael Wechner <mi...@wyona.com> wrote:
> I still receive from time to time "untranslated" on i18n stuff and it's not
> clear to me what the reason for this is. Any other people experiencing this?
[No research, just experience]
"untranslated" appears when key is the within the tag rather than a
property, and the key does not exist in the appropriate language file.
These return blanks:
<18n:text key="willNotBeFound"></18n:text>
<18n:text key="willNotBeFound"/>
This returns "untranslated":
<18n:text>willNotBeFound</18n:text>
"untranslated" also when i18n is used for a property, such as Value of
a Button. I guess the i18n tags are added around the label before it
passes through i18n. "untranslated" is very useful for debugging.
It should be easy to change i18n if that is desirable. If it is
changed, it would be better to keep the original text than set it to
blank, possible adding a mark to show it was supposed to be
translated.
I prefer the current method. It allows writing everything in the
default language, adding the i18n tags around phrases needing
translation, and seeing "untranslated" during testing. The <i18n:text
key="some-key"/> is useful for when you want a phrase to appear only
if a translation exists. It allows language-specific help, such as
"Click here to return to the default language", and satisfies customer
requests like "Can you add this option only to the German version of
the layout?"
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org