5 commits

Author	SHA1	Message	Date
Thiemo Kreuz	75016551e7	Rename formatNumNoSeparators() to localizeDigits() ... Because that is what it does. Note our method is different from the one in the Language class. We only accept strings. Change-Id: I39107e837cc29f2d7c8867c1e602aa643f9e1a57	2019-12-10 16:21:12 +01:00
Adam Wight	3d80501829	Narrow message localizer interface ... We never access Language directly, so proxy its method instead of returning the full object. I believe I've found a bug, but not fixing here: the footnote body numeric backlinks like "2.1" behave as if they were decimals rather than two numbers stuck together with a dot. So they are localized to "2,1". Bug: T239725 Change-Id: If386bf96d48cb95c0a287a02bedfe984941efe30	2019-12-06 12:17:09 +01:00
Adam Wight	b575835c63	Comments to help understand the message localizer ... Change-Id: Ic7c9a12a78f358d11d997abf9a3a8e996f451c8f	2019-12-05 09:06:37 +01:00
Adam Wight	c09d90aff3	Use message localizer in FootnoteBodyFormatter ... Makes the class more easily testable. Patch also changes an integration test into a unit test. Change-Id: I545730404aceed7e3857d96f4fd3c1b0a900c0c2	2019-12-04 13:41:44 +01:00
Adam Wight	bccb92335f	Introduce ReferenceMessageLocalizer ... Encapsulate the language interfaces, this will be used to replace global wfMessage calls in future patches. Change-Id: I7857f3e5154626e0b29977610b81103d91615f65	2019-12-04 13:40:05 +01:00