On Aug 28, 2008, at 6:42 AM, Robert Hanson wrote:
Jonathan, before Angel gets going, you should check over this list
in WebExport and see if it suffices. Get the wording and
punctuation just the way you want. If you need more translations,
just follow my lead here. I put the file
On Aug 28, 2008, at 8:22 AM, Angel Herráez wrote:
A single caveat: it seems that the compressing large data file to
message is no longer
appearing at the log. The file gets compressed and sevaed correctly.
Please, check that, Jonathan.
Angel,
Are you sure that it is not using
On 29 Aug 2008 at 12:14, Jonathan Gutow wrote:
Angel,
Are you sure that it is not using already compressed files? We try
to just copy files we've already processed. Try again starting from
scratch with a new file and let me know. It looks like it works for me.
You're right, I
On Aug 27, 2008, at 7:50 PM, Robert Hanson wrote:
another option is even better, I think. We just set up a set of GT._
(...) terms in Jmol and then bulk-load them into the JavaScript on
the fly. In the JavaScript we simply put in a set of keys, like
$MSG1$ that are then replaced on
Actually, I was thinking, this is quite tricky to set up. I've checked in
modifications. The templates and .js have no English text now.
Jonathan, before Angel gets going, you should check over this list in
WebExport and see if it suffices. Get the wording and punctuation just the
way you want.
On 11.6.RC10, the Export to Web module fails to save the template files.
On the saved folder, I only have JmolPopIn.js, the PNG file and the SPT file.
Error in the Jmol Java console is
couldn't find file: pop_in_template
I think this has something to do with the recent changes to make this
On Aug 27, 2008, at 9:24 AM, Angel Herráez wrote:
On 11.6.RC10, the Export to Web module fails to save the template
files.
On the saved folder, I only have JmolPopIn.js, the PNG file and the
SPT file.
Error in the Jmol Java console is
couldn't find file: pop_in_template
I think this
Thanks bob.
On Aug 27, 2008, at 9:43 AM, Robert Hanson wrote:
fixed for RC11 -- thanks for spotting that Angel.
Dr. Jonathan H. Gutow
Chemistry Department [EMAIL PROTECTED]
UW-Oshkosh
fixed for RC11 -- thanks for spotting that Angel.
On Wed, Aug 27, 2008 at 9:24 AM, Angel Herráez [EMAIL PROTECTED] wrote:
On 11.6.RC10, the Export to Web module fails to save the template files.
On the saved folder, I only have JmolPopIn.js, the PNG file and the SPT
file.
Error in the Jmol
The fixes are working great. I'm getting fully-Spanish Export to Web
dialogs, help pages and template-based web pages.
But for it to be perfect, we need also the JmolPopIn.js to be localized
(JmolPopIn_xx.js), since it holds an important message, i.e. telling the user
to click in order to get
I would prefer not to have to translate JmolPopIn.js. I think we
should put the strings that need translating somewhere else. While
looking into this I found some other messages that end up in the
generated pages that should be translated. I will update the these.
I will try to do this
I've been poking around to see what options we might have.
Implementing something like GT_ is one option. Alternatively, can
we put the text that needs to be translated in an invisible div in
the templates and then use that text as the overlay text? Another
alternative would be to keep
On Aug 27, 2008, at 5:58 PM, Robert Hanson wrote:
why not just store it as JavaScript, say:
GT_SP_es.js
and then read that and stuff it in the HTML file the way we do
other replacements?
Bob
I think this is what makes sense. If I see where your going, it's
only necessary to define a
On 27 Aug 2008 at 16:34, Jonathan Gutow wrote:
While
looking into this I found some other messages that end up in the
generated pages that should be translated.
I haven't seen any more. It may be those which I have already worked on. I
haven't
commited them yet since I wanted to check
On Aug 27, 2008, at 6:32 PM, Angel Herráez wrote:
On 27 Aug 2008 at 16:34, Jonathan Gutow wrote:
While
looking into this I found some other messages that end up in the
generated pages that should be translated.
I haven't seen any more. It may be those which I have already
worked on. I
another option is even better, I think. We just set up a set of GT._(...)
terms in Jmol and then bulk-load them into the JavaScript on the fly. In the
JavaScript we simply put in a set of keys, like $MSG1$ that are then
replaced on the fly. The GT system will recognize all these just like any
That seems like the answer. I may have some time to look into it
tomorrow. I have a few handouts to get ready for the start of
classes first, but I will see what I can do.
Jonathan
On Aug 27, 2008, at 7:50 PM, Robert Hanson wrote:
another option is even better, I think. We just set up a
17 matches
Mail list logo
