To add a single quote to the output text you should put '' (two single quotes) in the message format. Here is the MessageFormat detailssimonutp wrote:It seems that the ' makes the parser go mad.
Can we try to replace the incriminated text by
"Le tour de jeu de {o} commence."
which has no '.
MapTool 1.3 Development Build 62
Moderators: dorpond, trevor, Azhrei, Craig
Re: MapTool 1.3 Development Build 62
Re: MapTool 1.3 Development Build 62
I will try : C''est au tour de {0} de jouer.
It sounds really better in french.
It sounds really better in french.
Re: MapTool 1.3 Development Build 62
Thanks, jay; that's the page I was thinking of.
As noted on that page, we should probably copy/paste the description of single quotes into the translation file and provide the URL to the page as well. I don't think Trevor wants a b63 just for that, though.
As noted on that page, we should probably copy/paste the description of single quotes into the translation file and provide the URL to the page as well. I don't think Trevor wants a b63 just for that, though.
Re: MapTool 1.3 Development Build 62
There is going to be a B63 anyway because Trevor has a couple more little things to get out of the way.Azhrei wrote: I don't think Trevor wants a b63 just for that, though.
Notable mention: I am currently in a B62 game and so far it is rock solid! Man, macro speeds are blistering fast! Wooo!!!
How to use my bundled artwork (MT1.3B60+): http://forums.rptools.net/viewtopic.php?f=8&t=11759
Re: MapTool 1.3 Development Build 62
I haven't run a game with b62 yet, that is set for tomorrow night, but I did do a test on a problem macro and here is the results.
The macro is a Recovery macro that I thought was fairly basic. The problem was the more tokens you had run it at once, the time to complete grew exponentially. I did time tests on just my computer, not in the network. When I got to 10 tokens selected, it took slightly more then 2 minutes to complete. And that could easily happen in a large combat with a number of grunt NPCs.
In b62 I did the same test an with 10 tokens selected that same macro on the same computer now finishes in between 14 and 15 seconds.
This makes me very excited for my game tomorrow, as there promises to be a bit of combat. Thanks a bunch to everyone who put in the time debugging this!
The macro is a Recovery macro that I thought was fairly basic. The problem was the more tokens you had run it at once, the time to complete grew exponentially. I did time tests on just my computer, not in the network. When I got to 10 tokens selected, it took slightly more then 2 minutes to complete. And that could easily happen in a large combat with a number of grunt NPCs.
In b62 I did the same test an with 10 tokens selected that same macro on the same computer now finishes in between 14 and 15 seconds.
This makes me very excited for my game tomorrow, as there promises to be a bit of combat. Thanks a bunch to everyone who put in the time debugging this!
View MapTool video tutorials at RPToolsTutorials.net
Re: MapTool 1.3 Development Build 62
That is awesome news Brad! Thanks for sharing!
I am still in game - still not a single problem! Woooo!
I am still in game - still not a single problem! Woooo!
How to use my bundled artwork (MT1.3B60+): http://forums.rptools.net/viewtopic.php?f=8&t=11759
Re: MapTool 1.3 Development Build 62
I got through the whole night without any issues! Woohoo!!
How to use my bundled artwork (MT1.3B60+): http://forums.rptools.net/viewtopic.php?f=8&t=11759
Re: MapTool 1.3 Development Build 62
Fun fact: Dorpond is actually "Nature Boy" Ric Flair.
"You wanna be the build, you gotta BEAT the build! WOOOO!!!!"
"You wanna be the build, you gotta BEAT the build! WOOOO!!!!"
Re: MapTool 1.3 Development Build 62
*Lmao*
Now that is funny! Wooooo!
Now that is funny! Wooooo!
How to use my bundled artwork (MT1.3B60+): http://forums.rptools.net/viewtopic.php?f=8&t=11759
Re: MapTool 1.3 Development Build 62
Server Lock up still a problem! I locked up 2x tonight. Same symptoms. Players stopped receiving updates, weird blank error when you try to close maptools.
Re: MapTool 1.3 Development Build 62
Yeah, but the Boot code was removed from b62 and that's (supposedly) where the problem may lie. So taking out the updates certainly wouldn't fix anything but would put it back to square zero.
I didn't expect b62 to solve that issue.
I didn't expect b62 to solve that issue.
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
Re: MapTool 1.3 Development Build 62
Hmmm, that's not good.Sir Flak wrote:Server Lock up still a problem! I locked up 2x tonight. Same symptoms. Players stopped receiving updates, weird blank error when you try to close maptools.
Dreaming of a 1.3 release
Re: MapTool 1.3 Development Build 62
Well... on the positive side that means the boot code can probably go back in. On the negative side... that means the problem code still has to be found...
Loyalty is not blind, and it cannot be forced. It is a sincere bond formed out of respect and gratitude.
Re: MapTool 1.3 Development Build 62
Yeah, I've noticed the exponential growth (well actually I think it's geometric technically) in execution time of macros with multiple selected tokens.brad wrote: The macro is a Recovery macro that I thought was fairly basic. The problem was the more tokens you had run it at once, the time to complete grew exponentially. I did time tests on just my computer, not in the network. When I got to 10 tokens selected, it took slightly more then 2 minutes to complete. And that could easily happen in a large combat with a number of grunt NPCs.
In b62 I did the same test an with 10 tokens selected that same macro on the same computer now finishes in between 14 and 15 seconds.
B62 runs macros faster, but it still has this geometric growth problem for some odd reason.
You can for instance get a macro that takes 1 second to run on two tokens. Yet when you select 10 tokens, instead of taking 5 seconds to run, it'll take closer to 30-60 seconds. I noticed this anomaly for a long time and was hoping the new macro speed up code was going to fix that.
It seems it's still present but fortunately the macros run quite a bit faster now. The macro speed up code is awesome.