I did some messing around, and that is the only effect I've found so far that triggers that error...and only when using the Host targeting.Quote:
Originally Posted by zephp
Printable View
I did some messing around, and that is the only effect I've found so far that triggers that error...and only when using the Host targeting.Quote:
Originally Posted by zephp
When I write down and send characters ě, č or ř (or Ě, Č or Ř), it converts to strange characters (see the attached image).
https://i50.tinypic.com/2rqir61.jpg
Ě, Č and Ř are characters from our Middle-European language (Czech). They are standard characters in charsets Unicode (UTF-8), ISO-8859-1 and ISO-8859-2. Characters Š, Ž, Ý, Á and É are shown correctly.
Nevertheless, the error occures even in FG2 without 4E Ruleset.
Could you correct the fonts, please? I would be very grateful. Thanks in advance.
The problem in both FG and the 4e ruleset is probably because the font was created only with a specific set of characters. As such, I would guess that any ruleset would have a similar problem.
There is a Font tool on the Downloads page (and someone else is working on another version, but I'm not sure where that is) that could resolve your issue, but I believe that covering all font sets would be difficult. If the fonts themselves are publically available, having the Font Name and Size would help in this.
However, if the font itself does not contain these characters, you're back at square two (at least you know the name). You could find a font that is simililar that works with the characters in question.
Minor update today:
- Added bubble on character sheet upper right corner. Sets active identity on client, adds speaking identity on host.
- Updated button on character mini sheet to read "FULL" instead of "MINI"
- CT order sometimes different on client vs. host. Fixed.
- New button on Notes list was too low. Fixed.
- Script error when making attack while Marked. Fixed.
- Power reference window text overlap in certain situations. Fixed.
- Launcher. If convert button pressed without selecting ruleset, then Start button did not function as expected. Fixed.
Cheers,
JPG
I think they problem maybe down to the fact those characters that are missing for you are part of the Latin Extended A/B character set. The fonts in the 4E ruleset your using are based on the US/English Basic Latin character set which does not include those 3 characters.Quote:
Originally Posted by ShadoWWW
I'm not even sure if FGII supports anything other than the Basic Latin character set at the moment as well.
Either way if you grab the FGFont utility you can create and supplement any fonts/characters that you want. You can then either create an extension to override the default 4E ruleset fonts or you can simply edit the ruleset files directly to use your new fonts.
I know that some DMs like to use the portrait tokens, but prefer to have them as 50x50 rather than the default 32x32. Now that 4E has moved into a .pak that the updater auto updates, if you change the files in the .pak you would have to change them every time it updates. So, in case anyone is interested, I've created a little extension to make the portrait tokens 50x50 without having to worry about changing the .pak after an update. If anyone wants it, please let me know and I'll post it up for everyone.
Currently FG only supports ANSI internally, not unicode so all rulesets would have the problem. I do believe unicode support is on the wish list I don't know how high a priority it is.Quote:
Originally Posted by ShadoWWW
It may be that I am being naive here and that this is a feature of the test environment but it seems to me that moon_wizard is able to deliver fixes and updates very easily through the updater app. Given that, is there not a case for moving v2.0 of 4E_JPG out of Test and into Release?
Being that this is an official produce now, the purpose of the test environment is to make sure that the produce is as bug-free as it can possibly be before he releases it to the live environment. When he's satisfied that he's gotten everything he can (which, generally speaking, will probably be everything that's reported here plus anything he finds himself in the meantime) I'm sure he'll release it to the public. I don't think there's much, if anything, in the way of fixes needed though, but I don't know if anyone has reported anything else in PM.Quote:
Originally Posted by DNH
As Darkfaith mentioned, it boils down to when I feel that the ruleset is ready for prime time. Given that this version of 4E will see a huge increase in distribution, I want to spend a little extra time in testing.
Right now, it seems like the ruleset is settling in nicely. There were a few underlying issues to iron out, with a few more bugs shaken out, which I'm glad that I was able to address before release. Based on the information I'm seeing, it will probably be another week or so before it's ready (barring any major issues).
I want to keep the release version as stable as I can, without having to update the code every couple weeks with fixes.
A big thanks to everyone that has helped test so far!
Cheers,
JPG