lule
November 28th, 2012, 19:21
Background:
We started to develop an existing ruleset for the German system called “Das Schwarze Auge” (The black eye) further. The old team, which developed the ruleset stopped developing about a year ago. The ruleset is compatible with the root-version 2.0. This caused some problems after updating Fantasy Grounds to 2.9 and later. This is the reason why a new team started a few months ago with the enhancements. We gave the ruleset a new name in base.xml so that people can easily have both versions of the ruleset on their computer (the old-version and the version we are developing further). We also created a replaces-tag with the name of the old ruleset in base.xml.
Problem:
When people try to convert their campaigns to the new version of the ruleset they get the following error-message (this is just an example):
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Schloß.jpg
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Mühle.png
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Schloß.jpg
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Mühle.png
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Schloß.jpg
The problem was, that the pictures could not be opened on client-side.
We tested a lot to find the problem, which caused the failure. In the end we found, that the problem is caused through umlauts and other special characters in the file names of pictures and the bitmap-tags in the db.xml. When we replaced the problematic characters in both (picture-file-name and bitmap-tag in db.xml), the problem did not occurred. The Problem only occurred, when an old campaign has been converted to the new ruleset. Therefore we think that there is a problem in the converting routine connected with umlauts and other special characters in file names. Other special characters, for example in the name-tags, are not the problem, only in the bitmap-tags they cause this problem.
We hope that we could describe the error and our analyse in a proper way, that help you to develop the converting routine further.
We started to develop an existing ruleset for the German system called “Das Schwarze Auge” (The black eye) further. The old team, which developed the ruleset stopped developing about a year ago. The ruleset is compatible with the root-version 2.0. This caused some problems after updating Fantasy Grounds to 2.9 and later. This is the reason why a new team started a few months ago with the enhancements. We gave the ruleset a new name in base.xml so that people can easily have both versions of the ruleset on their computer (the old-version and the version we are developing further). We also created a replaces-tag with the name of the old ruleset in base.xml.
Problem:
When people try to convert their campaigns to the new version of the ruleset they get the following error-message (this is just an example):
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Schloß.jpg
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Mühle.png
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Schloß.jpg
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Mühle.png
Runtime Error: Cache file write error: +C:/Users/**/AppData/Roaming/Fantasy Grounds II/cache/Beo-WdS/campaign.dat - campaign/images/Schloß.jpg
The problem was, that the pictures could not be opened on client-side.
We tested a lot to find the problem, which caused the failure. In the end we found, that the problem is caused through umlauts and other special characters in the file names of pictures and the bitmap-tags in the db.xml. When we replaced the problematic characters in both (picture-file-name and bitmap-tag in db.xml), the problem did not occurred. The Problem only occurred, when an old campaign has been converted to the new ruleset. Therefore we think that there is a problem in the converting routine connected with umlauts and other special characters in file names. Other special characters, for example in the name-tags, are not the problem, only in the bitmap-tags they cause this problem.
We hope that we could describe the error and our analyse in a proper way, that help you to develop the converting routine further.