Hello!
I still find it cumbersome working with national characters in Webuilder 2015.
For me its: æøåÆØÅ
I have auto-correct set up, but this requires much back and forth (empty spaces required)
And I have snippets set up. But this to is not very fluid workflow.
Best would be auto-correct that not needed spaces before or after,
optional between html-tags only (content)
Better national character support
Moderator: kfury77
Forum rules
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
- Do not create new topics for already requested features. Add your comments to the existing feature request topics instead;
- Create separate topic for each feature suggestion. Do NOT post a number of non-related feature suggestions in a single topic;
- Give your topic a meaningful title. Do NOT create topics with meaningless titles, such as "My Suggestion" or "My Problem".
Better national character support
www.g-sun.no/en/
Re: Better national charackter support
We also use national characters for web development work here but we never use entities. That's what UTF-8 was invented for. Why not just use UTF-8 everywhere?
Blumentals Software Programmer
Re: Better national character support
Yep, as Aivars suggested it's much better if you save everything as UTF-8. In your HTML files be sure to add the meta tag
just under the tag in your pages.
Code: Select all
<meta charset="utf-8">
Code: Select all
<head>
Re: Better national character support
Sorry for late reply!
Thanks!
But I've tried utf-8 and it doesn't work for my asp-include-page.
Thanks!
But I've tried utf-8 and it doesn't work for my asp-include-page.
www.g-sun.no/en/
Re: Better national character support
It should work regardless of whether it's asp or anything else, just make sure that all site is utf-8 (you can't mix utf-8 and local encodings) and that you have appropriate meta encoding set. If you use database or other imported data, that should be in utf-8, too. It might not be viable to convert the existing site to utf-8, depending on how big and complex it is, but for future projects you should really think about using utf-8, that will save a lot of headache.
Blumentals Software Programmer