Editorial policy
Last updated
This page describes how content on yizhiweb.top is produced. It applies to every tool page, guide and reference table on the site. Last updated: 21 October 2026.
What we publish
We publish small browser-based tools and the explanation that goes with them. Our scope is narrow on purpose: converting between character sets, numeral systems and data formats, cleaning and normalising text, encoding and inspecting values, and explaining exactly which rule was applied. We do not publish news, opinion, medical, legal or investment content.
How content is produced, including automation
Tool behaviour is deterministic code, not generated prose. The conversion logic is written and reviewed by us against the standards listed on the methodology page, and the code that runs in your browser is the same code that runs in our test set.
We do use automation, and we say so. Reference tables that follow directly from a standard — for example the twenty-two numeral digit sets, which are ten consecutive Unicode code points each — are generated from the Unicode data rather than typed by hand, precisely because generating them removes transcription errors. The surrounding explanation, the method section, the worked examples and the FAQ answers are written by the editorial team and checked against the released code. We do not publish machine-translated bulk pages, and we do not publish pages whose only purpose is to occupy a search result.
Sourcing
Wherever a rule has an authoritative definition, we cite it: the Unicode Standard and the Unicode Character Database, RFC 3629 for UTF-8, national orthography references for language-specific rules, and the documented behaviour of spreadsheet functions where we quote a formula. Sources are listed at the foot of every tool page.
Review before publication
- The conversion function is implemented with no third-party dependencies.
- It is tested against the published examples and against edge cases, including invalid input.
- The method section is written to match what the code actually does, not what it was intended to do.
- Every example printed on the page is executed and must match the released output.
Corrections
If a result is wrong, we want to know. Write to the address on the contact page with the page URL, the exact input, the result you saw and the result you expected. A confirmed defect is fixed in the code, the case is added to the test set so it cannot regress, and the page's last-updated date changes. We do not silently edit a page to make it look newer.
Advertising
The site is funded by advertising. Advertisements are visually separated from content, are never placed inside a tool's interaction area, and are never presented as part of the interface. We do not accept payment for a favourable result, and no advertiser influences what a tool computes or what a page says.
Privacy
Tools run in your browser. Text you paste is never transmitted to us. See the privacy policy for the full detail.
What we will not publish
The clearest way to describe a policy is by its refusals. These are the categories we have decided not to publish, and why:
| Not published | Reason |
|---|---|
| A tool whose rule we cannot state | If the conversion cannot be described and checked against a reference, a correct result cannot be distinguished from a plausible one. |
| A tool that would have to guess | Reading kanji, inferring a word's meaning, or picking a transliteration convention without being told are all guesses, not conversions. |
| Aggregated or rewritten copy | A page that restates the top search results adds nothing, and the reader is better served by those results. |
| Machine-translated bulk pages | An unedited translation is a thin page in every locale it is published in. |
| Padded text to reach a length | Filler is itself a low-value signal; a shorter page that answers the question is better than a longer one that does not. |
| Fabricated examples or data | Every number printed on a page is produced by the released code, not written by hand. |
Authorship and accountability
Content is written by the same team that builds the tools, and the authors page describes the split of responsibilities. There is no anonymous contributor model and no outsourced copy: an explanation of a conversion rule is written by someone who can read the implementation and change it if the explanation is wrong.
Pages carry a last-updated date. It changes when the content or the behaviour it describes changes — not on a schedule, and not to make a page look fresh. A page whose date is old and whose content is accurate is in better standing than one whose date is current and whose description has drifted.
How the guides differ from tool pages
A tool page answers one question quickly: what this does, the rule it applies, an example. A guide answers the question that needs prose — which option to choose, why the obvious choice is sometimes wrong, and what goes wrong in practice. Both are written to the same standard, and a claim in a guide is checked against the same implementation the corresponding tool uses.
One consequence worth stating: if a guide and a tool ever disagree, the tool is authoritative and the guide is wrong. That has happened — a version difference in a YAML parser was described incorrectly in a draft, and the guide was corrected to match the implementation rather than the other way round.
Independence
No advertiser, vendor or affiliate partner has any influence over what is published or how a result is described. There are no sponsored tool pages, no paid placement in the catalogue, and no affiliate links inside tool output. Advertising on the site is display advertising, sold by a network, and is visually separate from the content.
Accessibility and readability
Pages are written in plain English, with the standard or algorithm named rather than paraphrased into vagueness. Tables have header cells marked with scope, results are announced to screen readers where a value updates, and every control has a label. If a page is hard to use with a keyboard or a screen reader, that is a defect — the contact page is the place to report it.
Questions about this page? Contact us.