My latest commits make the Jewel and JewelJS SWC files match between my
macOS and Windows machines. I ended up having to switch to a different
Maven Sass plugin because I realized the one we were using was no longer
maintained, and it was misbehaving. This new plugin is based on the newer
Sass
I ended up skipping the compiler option. Instead, [Embed] metadata with
mimeType="text/plain" can now optionally specify a charset attribute.
[Embed(source="file.txt",mimeType="text/plain",charset="CP1250")]
public var file:String;
To me, this makes more sense than a compiler option, since
According to the compiler docs, .properties files are assumed to be UTF-8.
https://github.com/apache/royale-compiler/blob/apache-royale-0.9.9/compiler/src/main/java/org/apache/royale/compiler/internal/resourcebundles/PropertiesFileParser.java#L98-L100
--
Josh Tynjala
Bowler Hat LLC
Yuck. Feel free to provide an example.
Isn't the CSS parsed by the compiler? Maybe it can be "normalized" there?
-Alex
On 4/6/23, 10:23 AM, "Josh Tynjala" mailto:joshtynj...@bowlerhat.dev>> wrote:
EXTERNAL: Use caution when clicking on links or opening attachments.
> The Maven build at
> The Maven build at some point was updated to force Sass to output CRLF on
Windows
> Unfortunately, this breaks the ability to do a cross-platform
reproducible build because every other platform uses LF
I should add an important detail to this. Technically, the SWC writer
converts CRLF to LF for
Some more findings:
The difference in Jewel appears to be caused by defaults.css. The Maven
build at some point was updated to force Sass to output CRLF on Windows, to
keep Git from saying that the file is modified after regenerating it.
Unfortunately, this breaks the ability to do a
