张小白
5103995c32
Previously, `DirectWrite` had been following the text system implementation on `macOS`, using the font's postscript name to differentiate between different font faces. However, I noticed occasional rendering issues, such as fonts incorrectly rendering as italics. Later, I discovered that on `Windows`, the postscript name is **not** unique. Surprisingly, even the same font can have different postscript names on macOS and Windows! It's hard to believe! The postscript name of a font face should be obtained from the same font table. Why would the same font face have different names? For example, the postscript name of ZedMono on `macOS` is `Zed-Mono-Bold-Extended-Italic`, while on `Windows`, it is `Zed-Mono-Extended`, missing weight and style information, leading to incorrect rendering. This PR introduces a `FontIdentifier` struct to uniquely identify font faces. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew install --cask zed@preview
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.