ec27228a8e
Em dashes (—) and en dashes (–) had spread across comments, docs, tests, and a few UI strings, reading as AI-generated boilerplate rather than house style. Replaced each with punctuation matching its context: colon for explanatory clauses, comma for asides, plain hyphen for numeric/legal ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for paired-dash asides. messages/en.json and messages/sv.json were fixed by hand together to keep sv/en in sync. Left untouched where the dash is the functional subject rather than decorative punctuation: date-range-parser.ts's separator regex, charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the agent system-prompt files that already instruct against em dashes, and a golden iXBRL test fixture compared byte-for-byte. Also fixes two bugs surfaced along the way: an off-by-one in ApiKeysPanel's scope-label split (a leftover from an earlier partial pass), and a charset-repair test that had lost the literal en-dash it exists to verify. Regenerated the agent atom seed migration (skills:generate) since 27 SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes, with an explicit carve-out for the functional-dash cases above. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
21 lines
591 B
TypeScript
21 lines
591 B
TypeScript
'use client'
|
|
|
|
import { useLocale } from 'next-intl'
|
|
import { formatDateLong as formatDateLongRaw } from '@/lib/utils'
|
|
|
|
/**
|
|
* Client-side hook returning locale-aware formatters.
|
|
*
|
|
* Currency stays SEK with sv-SE conventions (1 234,56 kr) regardless of UI
|
|
* language: that's the Swedish accounting standard, not a UI string.
|
|
* formatDate (ISO yyyy-MM-dd) is locale-independent and exported directly
|
|
* from lib/utils.
|
|
*/
|
|
export function useFormat() {
|
|
const locale = useLocale()
|
|
return {
|
|
locale,
|
|
formatDateLong: (date: Date | string) => formatDateLongRaw(date, locale),
|
|
}
|
|
}
|