Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
visionx:faq_tech [2023/11/07 17:30] admin |
visionx:faq_tech [2024/01/10 09:39] admin [Different Windows file encodings] |
||
---|---|---|---|
Line 181: | Line 181: | ||
==== Update export doesn't contain custom folders ===== | ==== Update export doesn't contain custom folders ===== | ||
- | The update export doesn't contain any files or folders. We automatically include following files and folders of WebContent directory: | + | The update export doesn't contain custom files or folders. We automatically include following files and folders of WebContent directory: |
<code bash> | <code bash> | ||
Line 210: | Line 210: | ||
Simply add your own includes and the update export will contain your custom files and directories as well. | Simply add your own includes and the update export will contain your custom files and directories as well. | ||
+ | |||
+ | ==== Different Windows file encodings ==== | ||
+ | |||
+ | Sometimes, you have the same Windows OS but different file encodings, e.g. cp1252 vs. UTF-8. This is not a VisionX problem, it's an OS setting. Some Windows installations have a new UTF-8 feature. You can see this option by going to Settings and then: All Settings -> Time & Language -> Language -> Administrative Language Settings | ||
+ | |||
+ | Will look like: | ||
+ | |||
+ | {{:visionx:utf8_windows.png?nolink&400|}} | ||
+ | |||
+ | Simply unset UTF-8 or set cp1252 instead of UTF-8 as described [[:visionx:faq_tech/#additional_jvm_start_parameters|here]]. |