4 commits

Author	SHA1	Message	Date
Thiemo Kreuz	0dc6f37785	Replace now unused native cloning feature ... Since I3db5175 the ParserCloned hook handler does not rely on cloning the Cite object any more. There is no cloning any more. This is dead code and we could remove it. Just to be sure I propose to keep the method, but let it throw an exception. Bug: T240248 Change-Id: I2057ea652ca25f4c7031c28a6e713671738f5e22	2019-12-20 20:07:59 +01:00
Adam Wight	084ca6b3d4	Integration parser test for ParserFunctions ... Depends-On: I09844079f163e583d3b1e941c701f8cda5029a0a Bug: T240345 Change-Id: I86c55ff88d9f4b800e8868728dfec6b4ceda82c2	2019-12-11 08:58:58 +01:00
Thiemo Kreuz	54333c9bd6	Stop formatting "1.2" as "1,2" in languages like German ... The new extends="…" feature is using numbers like "1.2". These should be localized in languages like Hebrew that uses other symbols for the digits. But the "." should not change. The existing feature when a <ref> is reused multiple times does have the same "issue". But it seems this is intentional, because it is covered by a test. Note this is not visible in German, because German uses custom labels "a", "b", and so on. This patch also improves the so called "smoke" tests and makes one cover numbers up to "1,10" for a <ref> that is reused that often. Bug: T239725 Change-Id: Iffcb56e1c7be09cefed9dabb1d6391eb6ad995ce	2019-12-04 09:43:04 +01:00
Thiemo Kreuz	38a38ae472	Add smoke tests for previously uncovered combinations ... I noticed a possible issue related to the $this->refSequence counter in the patch Ida9612d. Some of these counters might get messes up, but there was never a test that checked what will happen to the *next* reference then. I checked the test cases in this patch with a very old version of the codebase. Change-Id: If6e56f727dce5d0e5e38e048e602437597248a42	2019-11-27 16:34:46 +01:00