Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rules for special characters #30

Open
OleSan opened this issue Jun 2, 2015 · 3 comments
Open

Rules for special characters #30

OleSan opened this issue Jun 2, 2015 · 3 comments

Comments

@OleSan
Copy link
Contributor

OleSan commented Jun 2, 2015

We get a few creatives where the there are problems with special characters. Should we recommend that they are written in HTML code?

Example:

å = å 

That should guarantee that it will work on all sites. Most should run with UTF-8 today, but you're not sure if you make it for more than one site.

Included meta info in HTML files also get ignored by AdTech, at least when you upload it. It can be manually set by the traffic manager/ad operations manager, but that is an other source of human error when uploading it to the site.

Will this be to cumbersome for creative agencies? Is there a smarter way to go about this?

@gregersrygg
Copy link
Contributor

Yes, it could be a good idea to escape non-7-bit ASCII characters, but not all strings should be html-escaped. It depends on the output, but html is probably what is mostly used by ads.

@OleSan
Copy link
Contributor Author

OleSan commented Aug 19, 2015

So if we say something like this?

In HTML code, non-7-bit ASCII characters should be HTML escaped.

Ex:
På = På

@gadgetgnome
Copy link

Maybe also add that one should avoid special chars in code like @ & etc. We got some feedback from Tor Harald. Also that code shouldn't be minified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants