Skip to content

Commit f601f3e

Browse files
authored
Clarify AppleScript file encoding details in README
Updated the README to reflect changes in default character encoding for AppleScript files and added guidance for recovering from compiled binary data being saved in the AppleScript file by Apple's own Script Editor app's compile feature.
1 parent 2520fd0 commit f601f3e

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

README.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,9 @@ You can tweak the defaults for this package, `osacompile` and `osascript` in the
6969

7070
#### File Encoding
7171

72-
The default character encoding for AppleScript text files is [Mac Roman](https://www.wikiwand.com/en/Mac_OS_Roman). If you'd like to change this, you can just do so in the settings.
72+
In prior versions of macOS, the default character encoding for AppleScript text files was [Mac Roman](https://www.wikiwand.com/en/Mac_OS_Roman); it is now UTF-8.
73+
74+
If you are using this extension to edit old AppleScript text files, and your VS Code cannot open the files, you may need to change VS Code's default encoding for AppleScript files in the settings.
7375

7476
**Example:**
7577

@@ -81,6 +83,10 @@ The default character encoding for AppleScript text files is [Mac Roman](https:/
8183
}
8284
```
8385

86+
**Note:**
87+
88+
However, if an AppleScript file has been edited and compiled in Apple's Script Editor app, it saves the compiled binary into the same AppleScript file, making it unreadable in VS Code. To recover from this, open the AppleScript file in Apple's Script Editor app, and either copy the content from its UI, or use its File > Export to export the file as text-only file.
89+
8490
## License
8591

8692
This work is licensed under [The MIT License](https://opensource.org/licenses/MIT).

0 commit comments

Comments
 (0)