Release preparation: guide accuracy fixes, changelog, version bump

Author: kipcole9

CHANGELOG.md

@@ -4,7 +4,9 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [1.0.0-rc.7] — July 28th, 2026
+
+This release settles the `:format` / `:style` option naming across the library. The rule is now uniform: `:format` is how a **value** is rendered, `:style` is which variant of a **name or pattern** you get, and an option that selects something else again — `Localize.Interval`'s choice of which date fields appear — is named for what it selects. Every rename below is a hard break with no alias; each entry names its replacement.
 
 ### Changed
 
@@ -18,14 +20,16 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 * **Breaking:** `Localize.Interval.to_string/3` renames its `:style` option to `:fields`, because it selects *which* date fields appear (`:date`, `:month`, `:month_and_day`, `:year_and_month`) rather than a width — `:format` remains the width axis, and the two are now named for what they do. `Localize.Interval.date_styles/0` becomes `known_fields/0`, and `Localize.DateTimeIntervalFormatError` carries `:fields` with reason `:unknown_fields` in place of `:style` / `:unknown_style`.
 
-* `Localize.Calendar.display_name/3` reports an unusable `:style` as a `:style` error listing the widths the field actually has, instead of blaming the value: `display_name(:month, 3, style: :bogus)` said `value: 3, expected: "1..13"`. `style: :short` now resolves wherever CLDR carries it (the day parts) rather than silently returning `nil`.
-
 ### Documentation
 
 * `Localize.DateTime.to_string/2` documents its `:style`, `:date_format`, and `:time_format` options, which were live but absent from the docs. `:style` selects the date/time wrapper (`:at` renders "April 8, 2026 at 12:00:00 PM", and falls back to the standard wrapper for `:medium` and `:short`, which CLDR does not define it for).
 
 ### Fixed
 
+* `Localize.Calendar.display_name/3` reports an unusable `:style` as a `:style` error listing the widths the field actually has, instead of blaming the value: `display_name(:month, 3, style: :bogus)` said `value: 3, expected: "1..13"`. `style: :short` now resolves wherever CLDR carries it (the day parts) rather than silently returning `nil`.
+
+* `Localize.Unit.to_string/2` no longer lets a stray `:style` option reach the SI-prefix and custom-unit paths, where it produced "5 MegaJoule" for `style: :short` instead of the correct "5 Megajoule". The option has been ignored since 1.0.0-rc.0 and is now ignored everywhere, as documented.
+
 * `Localize.Duration.to_string/2` and `to_parts/2` join duration parts with CLDR's unit list patterns matched to the format width, per ECMA-402 `Intl.DurationFormat`, instead of the standard "and" conjunction: `:en` now renders "3 days, 2 hr" (was "3 days and 2 hr") and "3d 2h" for `format: :narrow`.
 
 * Per-compound units whose denominator carries a constant keep that count in every width: `curr-usd-per-30-day` renders "$10.00/30 days" for `format: :short`, where the denominator's precomposed `per_unit_pattern` ("{0}/d") previously swallowed the count and gave "$10.00/d". Counted denominators now compose through the locale's `compound.per` pattern, which also stops a numerator whose symbol contains the denominator noun being corrupted (narrow `candela-per-30-day` gave "10c30 d/30 d", now "10cd/30 d").

guides/interval_and_duration_formatting.md

@@ -44,30 +44,41 @@ iex> Localize.Interval.to_string(nil, ~D[2020-01-01], locale: :ja)
 
 The separator comes from CLDR's `intervalFormatFallback` pattern for the locale — most Western locales use an en-dash (`–`), Japanese uses a fullwidth tilde (`～`), and so on. Passing `nil` for both endpoints returns an error.
 
-### Styles and formats
+### Fields and formats
 
-The `:style` option controls which fields appear in the output:
+Two independent options shape the output. `:fields` selects *which* date fields appear:
 
-| Style | Description | Example skeleton |
-|---|---|---|
-| `:date` | Full date (default) | `:yMMMd` |
-| `:month` | Month only | `:MMM` |
-| `:month_and_day` | Month and day | `:MMMd` |
-| `:year_and_month` | Year and month | `:yMMM` |
+| Fields | Description |
+|---|---|
+| `:date` | The whole date (the default) |
+| `:month` | Month only |
+| `:month_and_day` | Month and day |
+| `:year_and_month` | Year and month |
 
-The `:format` option selects the detail level: `:short`, `:medium` (default), or `:long`.
+`:format` selects *how wide* those fields render: `:short`, `:medium` (the default), `:long`, or `:full`.
 
 ```elixir
 iex> {:ok, result} =
 ...>   Localize.Interval.to_string(~D[2022-04-22], ~D[2022-04-25],
 ...>     locale: :en,
-...>     style: :month_and_day,
+...>     fields: :month_and_day,
 ...>     format: :long
 ...>   )
 iex> String.contains?(result, "Fri") and String.contains?(result, "Mon")
 true
 ```
 
+The pair selects a CLDR skeleton. `Localize.Interval.known_fields/0` returns the mapping for the non-default selections; `:date` is resolved per-locale from the same table `Localize.Date.to_string/2` uses, so it has no fixed entry here:
+
+```elixir
+iex> Localize.Interval.known_fields()
+%{
+  month: %{short: :M, full: :MMM, long: :MMM, medium: :MMM},
+  month_and_day: %{short: :Md, full: :MMMEd, long: :MMMEd, medium: :MMMd},
+  year_and_month: %{short: :yM, full: :yMMMM, long: :yMMMM, medium: :yMMM}
+}
+```
+
 ### Intervals for times and datetimes
 
 `Localize.Interval.to_string/3` accepts `Date`, `Time`, `NaiveDateTime`, and `DateTime` values, as well as any map with the appropriate fields. The formatting strategy depends on what fields differ:
@@ -173,7 +184,7 @@ The `:except` option drops specific units from the output. By default, `:microse
 ```elixir
 iex> d = Localize.Duration.new_from_seconds(3665)
 iex> Localize.Duration.to_string(d, locale: :en, except: [:microsecond, :second])
-{:ok, "1 hour and 1 minute"}
+{:ok, "1 hour, 1 minute"}
 ```
 
 Other locales format durations using their native unit names and list separator:

guides/migration.md

@@ -101,8 +101,13 @@ Set the locale for the current process:
 iex> {:ok, _} = Localize.put_locale(:de)
 iex> Localize.get_locale().cldr_locale_id
 :de
+iex> {:ok, _} = Localize.put_locale(:en)
+iex> Localize.get_locale().cldr_locale_id
+:en
 ```
 
+The setting lasts for the life of the process, so the examples below reset it to `:en` first — otherwise every later result would come back in German.
+
 All formatting functions default their `:locale` option to `Localize.get_locale()`. In a Phoenix application you would typically call `Localize.put_locale/1` in a plug early in your pipeline.
 
 Use `Localize.with_locale/2` for temporary locale changes:

guides/number_formatting.md

@@ -126,9 +126,9 @@ Available RBNF rules vary by locale. Query them with:
 ```elixir
 iex> {:ok, rules} = Localize.Number.Rbnf.rule_names_for_locale(:en)
 iex> rules
-["spellout_cardinal", "spellout_ordinal", "digits_ordinal",
- "spellout_numbering", "spellout_numbering_year", "spellout_cardinal_verbose",
- "spellout_numbering_verbose", "spellout_ordinal_verbose"]
+["digits_ordinal", "spellout_cardinal", "spellout_cardinal_verbose",
+ "spellout_numbering", "spellout_numbering_verbose", "spellout_numbering_year",
+ "spellout_ordinal", "spellout_ordinal_verbose"]
 ```
 
 The root locale (`:und`) provides universal rules like `roman_upper`, `roman_lower`, `hebrew`, `ethiopic`, `greek_upper`, `greek_lower`, `armenian_upper`, `armenian_lower`, `cyrillic_lower`, `georgian`, and `tamil`.

lib/localize/calendar.ex

@@ -836,7 +836,11 @@ defmodule Localize.Calendar do
   * `part` is one of `:era`, `:quarter`, `:month`,
     `:day_of_week`, `:days_of_week`, or `:day_period`.
 
-  * `options` is a keyword list of options. See `localize/3`.
+  * `options` is a keyword list of options.
+
+  ### Options
+
+  See `localize/3` for the supported options.
 
   ### Returns
 

mix.exs

@@ -1,7 +1,7 @@
 defmodule Localize.MixProject do
   use Mix.Project
 
-  @version "1.0.0-rc.6"
+  @version "1.0.0-rc.7"
   @cldr_version_path "priv/localize/version"
   @localize_patch_version_path "priv/localize/localize_patch_version"