cvboucher
Posts: 191
|
| Posted: 11/06/2010, 10:27 AM |
|
I'm in the process of globalizing my VB.Net application. The locales I'll be using are English (Default), German and Japanese. There are a number of places where the output encoding can be set.
What should the Output Encoding be for each language (English, German and Japanese) and what should I set the Encoding to under Page Properties (General tab)? There's also the File Encoding and Default HTML Encloding in the Project Settings under Locales & Encodings. What should these be set to?
Thanks,
Craig
|
 |
 |
datadoit
|
| Posted: 11/07/2010, 6:26 AM |
|
Craig there are four different places to set the encoding so that all
will work well for you. That's right, four. I've put in a wish request
in the past to 'fix' this, if it's possible.
1. Project -> Settings -> Server/Script. Set Charset to utf-8.
2. Project -> Settings -> Locales & Encodings. Set File Encoding and
Default HTML Encoding to Unicode (UTF-8).
3. Project -> Settings -> Locales & Encodings -> Site Locales. For each
of your chosen languages, choose Edit, and then set the Output Encoding
to Unicode (UTF-8).
4. For each page in your project, right click on the page and choose
Page Properties, and set your Encoding there to Unicode (UTF-8).
In addition, it takes three clicks to get to your translations.
1. Project -> Settings (or the Project Settings toolbar button).
2. Locales & Encodings.
3. Translations.
I can't understand why there can't simply be a single toolbar or toolbox
button to launch you straight to number 3 above. Think I'll look into
creating one myself - could be possible with the SDK. In the meantime,
give us a vote on the wishlist item at:
http://forums.codecharge.com/posts.php?post_id=94380
|
|
|
|
cvboucher
Posts: 191
|
| Posted: 11/09/2010, 8:38 AM |
|
Thanks datadoit.
Craig
|
|
|
|
andrewi
Posts: 162
|
| Posted: 11/10/2010, 11:15 AM |
|
I agree about the button. I think the wishlist is closed to further votes, though.
Internationalisation is a great feature - and I use it all the time, regardless of whether another language will be needed. When you build a grid or form with the builders, all field captions, sorter names, etc get the name you want. So instead of having to change captions derived from field names (like "P Name" ) all over the place, you just have to enter a translation once. Improves consistency across pages, and of course if you need to rename anything site-wide it's easy.
And you can easily delete the resource fields if you don't want them. Nothing to lose, I think.
|
|
|
|
|
