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 s
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
other
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
> worke
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 chec
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 d
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
On 8/27/08, Jonathan Gutow <[EMAIL PROTECTED]> wrote:
>
> I've been poking around to see what options we might have.
> Implementing something like GT_ i
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
we can do way better -- and simpler. Just something like
GT = new Array()
GT_add("xxx","xxx")
GT_add("xxx","xxx")
GT_add("xxx","xxx")
GT_add("xxx","xxx")
GT_add("xxx","xxx")
GT_add("xxx","xxx")
then an overlay of the language-specific .js file instead of this one from
within Jmol and away we g
On Wed, Aug 27, 2008 at 11:47 PM, Robert Hanson <[EMAIL PROTECTED]> wrote:
> right -- the translations are only in the .html files. Jonathan, what we
> should do is create a GT equivalent for the JavaScript -- that is, a .js
> file that is inserted IF there is language dependence, and JavaScript t
right -- the translations are only in the .html files. Jonathan, what we
should do is create a GT equivalent for the JavaScript -- that is, a .js
file that is inserted IF there is language dependence, and JavaScript to
look up a phrase in that code.
Angel, maybe you can suggest a way of doing that
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
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 t
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 J
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 Office:
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 thin
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 module
The new top menu in the applet console has a "Help" entry which is not
localized.
Can this be done?
I find a couple of "Help" entries in
src/org/jmol/applet/Console.java
only one of them is properly capitalized as it appears in the menu, but it
hasn't got the key accelerator H marked as such,
Hi Angel,
On 8/27/08, Angel Herráez <[EMAIL PROTECTED]> wrote:
>
> Hi all
>
> 1)
> While pursuing a term that resisted proper translation (localization) in
> the pop-up menu, I've realized that there are about 60 GT terms duplicated
> in applet.PO and app.PO files.
>
Do you have a list of duplic
Hi all
1)
While pursuing a term that resisted proper translation (localization) in the
pop-up
menu, I've realized that there are about 60 GT terms duplicated in applet.PO
and
app.PO files.
The applet uses only GT terms from the applet.PO file.
The app uses the GT terms in the applet.PO file
19 matches
Mail list logo
