|
From: | John W. Eaton |
Subject: | Re: (The last) missing translation strings |
Date: | Sun, 24 Nov 2013 12:45:53 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131005 Icedove/17.0.9 |
On 11/24/2013 12:38 PM, Daniel J Sebald wrote:
On 11/24/2013 07:46 AM, Torsten wrote:On 24.11.2013 13:22, PhilipNienhuis wrote:[snip]What do we think about translating the contents of the "About Octave" pop-up? (Help | About Octave)Seems the tr () function was forgotten (long time ago) when implementing the about message. IMHO we should translate the "about" message.Just a question out of curiosity: what is the ramification of translation on, say, the community page where maybe the content of the window comes from a remote URL. Can that be translated?
To get the text to display in the community news window, Octave currently reads the URL http://octave.org/community-news.html. I considered having it look for http://octave.org/community-news-LANG.html first, then fall back on the default if no specific translation was found. Maybe we should do this, but this is a news page. It's something that could change frequently. I don't want to have to wait for translations to be completed before posting news, and I don't really want to increase the overhead of posting news by having to gather translations and place them on the web. I say we just go without translating the news page and see whether that causes problems before trying to solve a problem that might not be very important. jwe
[Prev in Thread] | Current Thread | [Next in Thread] |