1)
I use poEdit (Win) for translations --but we have to consider the new,
alternative, web-based
system on --. The PO files have an UTF8 coding, so it's not correct that I use
iso-8859-1as
Bob pointed out. I write directly the accented characters by keyboard and
poEdit codes them
as UTF8 (when
On Aug 30, 2008, at 5:15 AM, Angel Herráez wrote:
The footer is not much of a problem, as if can be either entered
with entities or fixed at the end in the wysiwyg editor by just
deleteing the offending character as typing the correct one --as
the rest of the GT that go into body--.
OK, so if it is necessary to use
aacute;
then we still have problems with regard to marking. You are saying that any
GT expressions headed toward HTML must be escaped in this HTML-only sort of
way. We are not set up to make such a distinction in the translations.
So, if this really is the
On 30 Aug 2008 at 9:49, Jonathan Gutow wrote:
You can look for yourself. By any chance does the Old
file look ok on your machine, which I assume defaults to Spanish?
Right. WinXP Spanish
The
files are:
Old (didn't work):
Two pages to check:
http://www.alanwood.net/demos/ent4_frame.html
http://www.fileformat.info/info/unicode/block/latin_supplement/utf8test.htm
question is whether the #; method works for you. If so, let's just go
with that and let translators translate as usual into unicode. I know that's
OK, here's another simple possibility. We simply change those character
codes entered by the translator or user that are going to HTML by converting
them to the hex value:
#x00E1;
for example. That way it's our job, not the translator's or user's job, to
manage this.
Bob
On Sat, Aug 30, 2008
On 30 Aug 2008 at 10:26, Robert Hanson wrote:
span /span
might. If that is in the GT expression, then the translator will see that
and, presumably, know to
use this mechanism. It isn't great, because it is nonstandard, but it seems
the only alternative.
Don't know yet what to vote
On Aug 30, 2008, at 10:59 AM, Angel Herráez wrote:
I still have a doubt: does the original version,trans test es
2.html
look also wrong for you when read it from local disk? Are you using
Mac?
I get the same result locally on a mac. I haven't tried the files
locally on Linux or
On 30 Aug 2008 at 11:52, Jonathan Gutow wrote:
I get the same result locally on a mac. I haven't tried the files
locally on Linux or Windows.
Aha!
I think that **generating** the page in the Mac may be the key.
I've just generated a page using an app with the old translation (that has
I added the method
GT.escapeHTML(String msg)
Translators do not need to do anything special in translating the HTML now.
If Angel wants, he can use aacute;, although I think but he can just as
well just do as he has been doing for all Jmol translations.
Users can enter the page title in
Sí, está perfecto. Muy interesante. Es posible.
On Sat, Aug 30, 2008 at 12:26 PM, Angel Herráez [EMAIL PROTECTED]wrote:
On 30 Aug 2008 at 11:52, Jonathan Gutow wrote:
I get the same result locally on a mac. I haven't tried the files
locally on Linux or Windows.
Aha!
I think that
Just added a couple more GT.escapeHTML() calls. Around the names of the
buttons and such.
On Sat, Aug 30, 2008 at 12:16 PM, Robert Hanson [EMAIL PROTECTED] wrote:
I added the method
GT.escapeHTML(String msg)
Translators do not need to do anything special in translating the HTML now.
If
I've commited another GT.escapeHTML() call, on the skeleton sentence at the
footer --
the one that started all this--
I changed every string in my local copy of es.PO file back to accents and
tested. Everything
working here OK --well, nearly, but I will leave that for later on; accents
are a
On Aug 30, 2008, at 2:44 PM, Angel Herráez wrote:
Jonathan, I'm not totally sure, but I seem to recall that this Mac-
specific way of encoding has happened to us before. Maybe that was
why I never could come to a conclusion about our problems with
characters after many tests. Pages
I like this idea. Unless someone, especially those doing
translation, objects I will do this in the following manner.
1) The beginning of strings will contain the following style =
hidden; The following text will show up in a web page. Please use
ANSI coding for special characters when
I'm not following what the idea is here. First let's confirm that it's
really an issue. I'm not having the problem. Jonathan is. Tagging
translations in any way is going to be problematic. We have the
GT_popup_template.html_x tags already. That's enough -- it indicates
that the tag is going to
On Aug 29, 2008, at 9:31 PM, Robert Hanson wrote:
I'm not following what the idea is here. First let's confirm that
it's really an issue. I'm not having the problem. Jonathan is.
Tagging translations in any way is going to be problematic. We have
the GT_popup_template.html_x tags
right -- translators only see what is between {}, but that is what must
appear as well. There's really no mechanism to tag these, so I would prefer
to leave them as is and figure out why your browser is not displaying
characters properly.
Bob
On Fri, Aug 29, 2008 at 10:15 PM, Jonathan Gutow
18 matches
Mail list logo
