The problem in question is that re-declaring the UTF-8 charset in ASP (it's already UTF-8 in the meta tags) makes some special characters show up properly and others not, and removing that declaration makes different characters show up correctly and others not.
I ended up removing the re-declaration and finding a VBScript function online that converts to UTF-8 and running the output from the RSS feed that supplies the news on the home page through it, which is what messes up when UTF-8 is not re-declared. Doesn't solve the problem that somehow stuff on our library database descriptions ends up going into the master database weirdly, so the output is extra-weird (probably, I am assuming, because everyone here composes in Word then pastes directly from that into fields) when it gets pulled out of that database. The ultimate solution is probably to sanitize the string before they're put into the master database, but (a) that won't clean up the data already in there and (b) that's all managed by a set of apps written and managed by my boss, so all I can do is point the issue out and suggest a solution.
(My perfect solution would be to ban Word from doing anything in any way related to the internet, but that's going to be a hard sell.)
The problem in question is that re-declaring the UTF-8 charset in ASP (it's already UTF-8 in the meta tags) makes some special characters show up properly and others not ...
I can see exactly where this is heading.
*reads on*
Okay, not the exact fillips, but yup, yup, yup. Especially that Word is somehow involved. UTF declarations somehow never work right without sanitizing.
Last time I re-upped my DW membership, I managed to forget the reason that I buy the most expensive package is the number of icons, and got the cheaper version, to save a bit of money. Which means for a while there I lost access to a bunch of the icons over on DW, including Mello's fabulous ass. I have it back now, though!
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
---L.
no subject
I ended up removing the re-declaration and finding a VBScript function online that converts to UTF-8 and running the output from the RSS feed that supplies the news on the home page through it, which is what messes up when UTF-8 is not re-declared. Doesn't solve the problem that somehow stuff on our library database descriptions ends up going into the master database weirdly, so the output is extra-weird (probably, I am assuming, because everyone here composes in Word then pastes directly from that into fields) when it gets pulled out of that database. The ultimate solution is probably to sanitize the string before they're put into the master database, but (a) that won't clean up the data already in there and (b) that's all managed by a set of apps written and managed by my boss, so all I can do is point the issue out and suggest a solution.
(My perfect solution would be to ban Word from doing anything in any way related to the internet, but that's going to be a hard sell.)
In conclusion: bah.
no subject
I can see exactly where this is heading.
*reads on*
Okay, not the exact fillips, but yup, yup, yup. Especially that Word is somehow involved. UTF declarations somehow never work right without sanitizing.
---L.
no subject
no subject
no subject
no subject
Mello's fabulous ass
RE: Mello's fabulous ass