Topic: NA - page 559. (Read 893616 times)
Would it be an idea to offer Guldencoin supporters the opportunity to buy mining shares? Ryan, the guy who is running http://nxtmining.com/ made this possible for EnergyCoin and that is working perfectly. Maybe Guldencoin could ask him to do the same for Guldencoin? It is a brilliant system: with NXT you buy mining shares. With these mining shares other coins are mined, and these coins are exchanged for the target coin (NLG) and every week the mining shareholders get dividend paid out in NLG. It would be great to have this available for Guldencoin, -I would certainly buy many NLG mining shares!
I think I fixed it.
I had to setup a dualboot with windows to reproduce the problem and found it pretty quick.. Apparently rendering fonts is still different between windows and linux/osx. It's a pretty technical problem, I'll spare you the details.
Bottomline: the font's exported from fontforge had some mistakes that -for windows- messed up rendering even though the font shouldn't be used for characters other than Ġ.. Fontsquirrel's webfont generator fixed that. (great tool: http://www.fontsquirrel.com/tools/webfont-generator)
It also added .eot fontfile (legacy windows IE support!).
I've learned that I shouldn't have released this font right away as 1.0 'release' stuff and I should have done some more research about cross-platform font rendering. Sorry for that.
I assume it's fixed for everyone now (after reload). Please let me know if there are still problems.
I had to setup a dualboot with windows to reproduce the problem and found it pretty quick.. Apparently rendering fonts is still different between windows and linux/osx. It's a pretty technical problem, I'll spare you the details.
Bottomline: the font's exported from fontforge had some mistakes that -for windows- messed up rendering even though the font shouldn't be used for characters other than Ġ.. Fontsquirrel's webfont generator fixed that. (great tool: http://www.fontsquirrel.com/tools/webfont-generator)
It also added .eot fontfile (legacy windows IE support!).
I've learned that I shouldn't have released this font right away as 1.0 'release' stuff and I should have done some more research about cross-platform font rendering. Sorry for that.
I assume it's fixed for everyone now (after reload). Please let me know if there are still problems.
Confirmed working. I had a hunch it had something to do with the font files in the CSS.
I'm sorry I could be more of a help today, got wrapped up at work pretty quick after our last PM. I'm glad you got it resolved though.
-Fuse
Good to see more additions for NLG! Nice work in getting that issue resolved.
I think I fixed it.
I had to setup a dualboot with windows to reproduce the problem and found it pretty quick.. Apparently rendering fonts is still different between windows and linux/osx. It's a pretty technical problem, I'll spare you the details.
Bottomline: the font's exported from fontforge had some mistakes that -for windows- messed up rendering even though the font shouldn't be used for characters other than Ġ.. Fontsquirrel's webfont generator fixed that. (great tool: http://www.fontsquirrel.com/tools/webfont-generator)
It also added .eot fontfile (legacy windows IE support!).
I've learned that I shouldn't have released this font right away as 1.0 'release' stuff and I should have done some more research about cross-platform font rendering. Sorry for that.
I assume it's fixed for everyone now (after reload). Please let me know if there are still problems.
I had to setup a dualboot with windows to reproduce the problem and found it pretty quick.. Apparently rendering fonts is still different between windows and linux/osx. It's a pretty technical problem, I'll spare you the details.
Bottomline: the font's exported from fontforge had some mistakes that -for windows- messed up rendering even though the font shouldn't be used for characters other than Ġ.. Fontsquirrel's webfont generator fixed that. (great tool: http://www.fontsquirrel.com/tools/webfont-generator)
It also added .eot fontfile (legacy windows IE support!).
I've learned that I shouldn't have released this font right away as 1.0 'release' stuff and I should have done some more research about cross-platform font rendering. Sorry for that.
I assume it's fixed for everyone now (after reload). Please let me know if there are still problems.
Confirmed working. I had a hunch it had something to do with the font files in the CSS.
I'm sorry I could be more of a help today, got wrapped up at work pretty quick after our last PM. I'm glad you got it resolved though.
-Fuse
yeah I'm running that...
Thing is I can't reproduce the problem!
Whithout being able to reproduce I'm kinda blind and cannot see where this comes from.
It indeed looks like some styling problem...
I have exactly the same chrome version but running on linux. I can't think of a reason why css rules would apply different between OS platforms..
@ny2cafuse: can you see what's causing this?
Thing is I can't reproduce the problem!
Whithout being able to reproduce I'm kinda blind and cannot see where this comes from.
It indeed looks like some styling problem...
I have exactly the same chrome version but running on linux. I can't think of a reason why css rules would apply different between OS platforms..
@ny2cafuse: can you see what's causing this?
OK... it's an issue with the guldencoin font-family declaration. Removing "guldensign" from the body and H1-6 font-family tags clears up the errors. I just need to tinker a bit more to see what the resolution is.
If you beat me to it, just let me know.
-Fuse
I think I fixed it.
I had to setup a dualboot with windows to reproduce the problem and found it pretty quick.. Apparently rendering fonts is still different between windows and linux/osx. It's a pretty technical problem, I'll spare you the details.
Bottomline: the font's exported from fontforge had some mistakes that -for windows- messed up rendering even though the font shouldn't be used for characters other than Ġ.. Fontsquirrel's webfont generator fixed that. (great tool: http://www.fontsquirrel.com/tools/webfont-generator)
It also added .eot fontfile (legacy windows IE support!).
I've learned that I shouldn't have released this font right away as 1.0 'release' stuff and I should have done some more research about cross-platform font rendering. Sorry for that.
I assume it's fixed for everyone now (after reload). Please let me know if there are still problems.
yeah I'm running that...
Thing is I can't reproduce the problem!
Whithout being able to reproduce I'm kinda blind and cannot see where this comes from.
It indeed looks like some styling problem...
I have exactly the same chrome version but running on linux. I can't think of a reason why css rules would apply different between OS platforms..
@ny2cafuse: can you see what's causing this?
Thing is I can't reproduce the problem!
Whithout being able to reproduce I'm kinda blind and cannot see where this comes from.
It indeed looks like some styling problem...
I have exactly the same chrome version but running on linux. I can't think of a reason why css rules would apply different between OS platforms..
@ny2cafuse: can you see what's causing this?
OK... it's an issue with the guldencoin font-family declaration. Removing "guldensign" from the body and H1-6 font-family tags clears up the errors. I just need to tinker a bit more to see what the resolution is.
If you beat me to it, just let me know.
-Fuse
yeah I'm running that...
Thing is I can't reproduce the problem!
Whithout being able to reproduce I'm kinda blind and cannot see where this comes from.
It indeed looks like some styling problem...
I have exactly the same chrome version but running on linux. I can't think of a reason why css rules would apply different between OS platforms..
@ny2cafuse: can you see what's causing this?
Thing is I can't reproduce the problem!
Whithout being able to reproduce I'm kinda blind and cannot see where this comes from.
It indeed looks like some styling problem...
I have exactly the same chrome version but running on linux. I can't think of a reason why css rules would apply different between OS platforms..
@ny2cafuse: can you see what's causing this?
[..]
I can confirm that this happens to me as well on Chrome. No form of refresh helps.
-Fuse
I can confirm that this happens to me as well on Chrome. No form of refresh helps.
-Fuse
Very anoying that I can't reproduce this.
What OS and Chrome version are you using?
Can you please try this:
- ctrl+shift+i
- click on "Network"
- right-click in the list of network activities (can be empty, that doesn't matter)
- click on "Clear browser cache" (not cookies)
- refresh the page
If this still doesn't work, please let me know what OS and Chrome version are you using?
There was a short problem with the top bar that caused something like this. But it was fixed a while ago (could mabye survive in cache though..).
I don't understand how the guldensign being added to the docs could mess it up like this..
unfortunately on http://nlgcup.com/#/match/W57vW58 the Guldencoin sign is messed up into Ġ
This is fixed. Just let the caches time out or force a reload with ctrl+F5.
unfortunately on http://nlgcup.com/#/match/W57vW58 the Guldencoin sign is messed up into Ġ
ShopemNL,
Thanks for the screenshot, I'm trying to reproduce.
Does refreshing cache (ctrl+F5) fix this for you?
Is it only the guldencoin page in the docs?
Thanks!
Thanks for the screenshot, I'm trying to reproduce.
Does refreshing cache (ctrl+F5) fix this for you?
Is it only the guldencoin page in the docs?
Thanks!
I can confirm that this happens to me as well on Chrome. No form of refresh helps.
-Fuse
https://docs.guldencoin.com/guldensign/ messes up in Chrome?
What's the problem?
coin dying ?
One of the latest updates from the dev. So we might get some big news this week.
why is it so quiet today?
Its a very hot day... So most dutch people are probably outside. We are inside... working on something very nice.coin dying ?
If this coin is dying then every other coin is already dead and I mean every other alt coin
On the other hand I was expecting more merchants already considering the impressive start it had but the devs did explain it might take 2 months or so before more merchants will be added... we should be close to that point now.
coin dying ?
Ha, ha, get a life my friend. Instead of posting the same message in every coin ANN do something positive in cryptoworld. If you want to spread FUD try somewhere else.
Jump to: