-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse EngineData #6
Comments
Hello, I'm currently working at OpenDesign on PSD parsing. We'd love to use your library, but first, there are some features that are needed. This is one of them. Would it be ok with you if I started implementing it or is there something I should know beforehand? I can either create a new parser in TS, in Rust, or use the existing npmjs library - your call :) |
Hello @scoiatael, There is nothing you need to know beforehand. If you post a pull request, we will actively review it. |
We got an internal request regarding the "EngineData" field of the Type Tool Object Setting structure, which encodes information about a text layer.
The Type Tool Object Setting structure is part of the Additional Layer Information record, inside the Layer and Mask Information Section of a PSD file.
The EngineData field is encoded in an undocumented format (nicknamed "EngineData format") invented by Adobe. While
@webtoon/psd
does not currently parse this segment, we may have to do so in the future, in order to support additional features related to text layers.Prior work
Several PSD parsers can handle the EngineData format:
However, we MAY want to write a custom parser in TypeScript, in accordance with the Zero-Dependency design goal (see #5).
The text was updated successfully, but these errors were encountered: