printf/Cargo.toml

[package]
name = "fish-printf"
edition.workspace = true
rust-version.workspace = true
version = "0.2.1"
repository.workspace = true
description = "printf implementation, based on musl"
license = "MIT"

[dependencies]
libc = "0.2.155"
widestring = { version = "1.0.2", optional = true }
unicode-segmentation = "1.12.0"
unicode-width = "0.2.0"

[lints]
workspace = true
Add printf crate to workspace This adds a crate containing a new implementation of printf, ported from musl. This has some advantages: - locale support is direct instead of being "applied after". - No dependencies on libc printf. No unsafe code at all. - No more WideWrite - just uses std::fmt::Write. - Rounding is handled directly in all cases, instead of relying on Rust and/or libc. - No essential dependency on WString. - Supports %n. - Implementation is more likely to be correct since it's based on a widely used printf, instead of a low-traffic Rust crate. - Significantly faster. 2024-05-12 15:27:10 -07:00			`[package]`
Rename printf crate to fish-printf Preparing to publish to crates.io 2024-06-09 12:29:09 -07:00			`name = "fish-printf"`
Use workspace config in packages - Apply lint config to entire workspace - Inherit workspace config for fish-printf - Allow stdlib printing in fish-printf tests The current problem which is addressed by this is that warnings about C-String literals are generated by clippy for code in fish-printf. These literals are not available with the current MSRV 1.70, but previously the MSRV setting was not inherited by fish-printf, causing the warning to appear. 2025-05-02 20:19:29 +02:00			`edition.workspace = true`
			`rust-version.workspace = true`
Improve the README of the printf crate 2024-09-23 11:13:57 -07:00			`version = "0.2.1"`
Use `LocalizableString` for gettext This new wrapper type can be constructed via macros which invoke the `gettext_extract` proc macro to extract the string literals for PO file generation. The type checking enabled by this wrapper should prevent trying to obtain translations for a string for which none exist. Because some strings (e.g. for completions) are not defined in Rust, but rather in fish scripts, the `LocalizableString` type can also be constructed from non-literals, in which case no extraction happens. In such cases, it is the programmer's responsibility to only construct the type for strings which are available for localization. This approach is a replacement for the `cargo-expand`-based extraction. When building with the `FISH_GETTEXT_EXTRACTION_FILE` environment variable set, the `gettext_extract` proc macro will write the messages marked for extraction to a file in the directory specified by the variable. Updates to the po files: - This is the result of running the `update_translations.fish` script using the new proc_macro extraction. It finds additional messages compared to the `cargo-expand` based approach. - Messages IDs corresponding to paths are removed. The do not have localizations in any language and localizing paths would not make sense. I have not investigated how they made it into the po files in the first place. - Some messages are reordered due to `msguniq` sorting differing from `sort`. Remove docs about installing `cargo-expand` These are no longer needed due to the switch to our extraction macro. 2025-05-28 01:42:01 +02:00			`repository.workspace = true`
Add description and license to printf Cargo.toml 2024-06-09 12:20:05 -07:00			`description = "printf implementation, based on musl"`
			`license = "MIT"`
Add printf crate to workspace This adds a crate containing a new implementation of printf, ported from musl. This has some advantages: - locale support is direct instead of being "applied after". - No dependencies on libc printf. No unsafe code at all. - No more WideWrite - just uses std::fmt::Write. - Rounding is handled directly in all cases, instead of relying on Rust and/or libc. - No essential dependency on WString. - Supports %n. - Implementation is more likely to be correct since it's based on a widely used printf, instead of a low-traffic Rust crate. - Significantly faster. 2024-05-12 15:27:10 -07:00
			`[dependencies]`
Update nix to 0.29 2024-06-05 17:02:57 +02:00			`libc = "0.2.155"`
Clean up fish-printf in preparation for publishing Make fish-printf no longer depend on the widestring crate, as other clients won't use it; instead this is an optional feature. Make format strings a generic type, so that both narrow and wide strings can serve. This removes a lot of the complexity around converting from narrow to wide. Add a README.md to this crate. 2024-09-19 15:34:40 -07:00			`widestring = { version = "1.0.2", optional = true }`
Make printf unicode-aware Specifically, the width and precision format specifiers are interpreted as referring to the width of the grapheme clusters rather than the byte count of the string. Note that grapheme clusters can differ in width. If a precision is specified for a string, meaning its "maximum number of characters", we consider this to limit the width displayed. If there is a grapheme cluster whose width is greater than 1, it might not be possible to get precisely the desired width. In such cases, this last grapheme cluster is excluded from the output. Note that the definitions used here are not consistent with the `string length` builtin at the moment, but this has already been the case. 2025-05-03 01:43:53 +02:00			`unicode-segmentation = "1.12.0"`
			`unicode-width = "0.2.0"`
Use workspace config in packages - Apply lint config to entire workspace - Inherit workspace config for fish-printf - Allow stdlib printing in fish-printf tests The current problem which is addressed by this is that warnings about C-String literals are generated by clippy for code in fish-printf. These literals are not available with the current MSRV 1.70, but previously the MSRV setting was not inherited by fish-printf, causing the warning to appear. 2025-05-02 20:19:29 +02:00
			`[lints]`
			`workspace = true`