When a Mac text editor character count is used for a deadline, the governing rule must come first. If the deadline asks for a raw count that includes spaces and line breaks, the number to use for this specimen is 1,080. If the rule is full-width = 1, half-width = 0.5, and line breaks excluded, the comparison value is 980.0. The values differ because they answer different requirements, not because one calculation failed. If the destination’s rule is unknown, keep both values in separate fields and do not guess which one governs the deadline.
The specimen contained 900 Japanese characters, 100 ASCII characters, 60 half-width spaces, and 20 line breaks. Its raw count remained 1,080 after saving and reopening a named copy, and the SHA-256 matched. That Stage 4 result is passed. The 980.0 value is a local calculation from the same components, not a captured Rune Studio interface value.
The two totals answer different deadline rules
The raw count gives every included component a weight of one.
| Component | Quantity | Raw contribution |
|---|---|---|
| Japanese characters | 900 | 900 |
| ASCII characters | 100 | 100 |
| Half-width spaces | 60 | 60 |
| Line breaks | 20 | 20 |
| Total | 1,080 | 1,080 |
The weighted comparison gives Japanese characters a weight of 1, ASCII and half-width spaces a weight of 0.5, and line breaks a weight of zero.
| Component | Raw count | Weighted count | Difference |
|---|---|---|---|
| 900 Japanese characters | 900 | 900 | 0 |
| 100 ASCII characters | 100 | 50 | -50 |
| 60 half-width spaces | 60 | 30 | -30 |
| 20 line breaks | 20 | 0 | -20 |
| Total | 1,080 | 980.0 | -100 |
Because the difference of 100 can be reconciled, 980.0 should not be treated as an incorrect display of 1,080. Conversely, submitting 980.0 for a raw-count requirement applies weights that the requirement did not request.
Choose the deadline number before using it
There are three distinct decisions:
- If the destination includes every code point, including spaces and line breaks, use 1,080.
- If it explicitly uses full-width = 1, half-width = 0.5, and excludes line breaks, the formula here produces 980.0.
- If it says only “character count,” without defining spaces, line breaks, or half-width weight, do not choose either value. Record both and ask for the governing rule.
The larger or smaller editor number is not automatically safer. A deadline value must be linked to the destination’s formula, not selected by preference.
Keep both values tied to the same manuscript version
STUDIO-192 owns the generic method for defining a raw count, creating a known-component sample, and checking it after reopening. This article focuses on preventing two display rules from being merged.
- Freeze one manuscript version and one measured range.
- Record its raw count in a field labeled raw. The baseline here is 1,080.
- Apply the required weighting to the same version and record the result in a separate weighted field. The comparison here is 980.0.
- Reconcile the difference of 100 as ASCII -50, spaces -30, and line breaks -20.
- Use only the field that matches the destination’s rule as the deadline number.
- If the rule cannot be established, leave the decision unresolved while preserving the version and both values.
The save, reopen, and matching SHA-256 show that the raw baseline came from unchanged content. They do not establish that Rune Studio displayed 980.0 in a measured interface session.
Do not give Rune Studio’s two displays the same meaning
Current documentation for the Mac version of Rune Studio describes both a raw character count and a display that treats full-width characters as 1 and half-width characters as 0.5. That is a Stage 3 product capability.
The Stage 4 evidence verifies a raw count of 1,080 before and after reopening and a matching SHA-256. The 980.0 value was calculated locally from 900 Japanese characters, 100 ASCII characters, 60 spaces, and 20 line breaks. It must not be reported as a captured Rune Studio UI result or as two simultaneously measured interface values.
The two displays are not a universal correct-versus-incorrect pair. Raw count can serve as the baseline for all included components; a full-width/half-width display can serve a requirement that uses that weighting. The external destination determines which value matters.
Reconcile a mismatch before blaming either tool
If another service reports a different total, first determine whether it is being compared with 1,080 or 980.0. Then compare the exact range, space policy, line-break policy, and half-width weight one item at a time.
The difference of 100 is fully explained for this specimen. Any unexplained remainder may require a separate check for combining sequences, multi-code-point emoji, excluded headings, or notes. The current specimen contains no combining sequences or composite emoji, so their treatment remains unverified.
No external service was tested for either 1,080 or 980.0. If its number differs, test the same short string under both published rules before declaring Rune Studio or the service incorrect.
The role differs from STUDIO-192
STUDIO-192 centers on defining raw characters, preparing a known sample, and reading the same raw value from a reopened delivery copy.
This article centers on the decision made when the same version yields 1,080 raw and 980.0 weighted. Its specific work is to reconcile the 100-character difference and select only the value whose formula matches the deadline. The raw-baseline tutorial remains with STUDIO-192.
Conclusion: choose 1,080 or 980.0 from the stated rule
Use 1,080 when the deadline requires a raw count including spaces and line breaks. Use 980.0 only for the stated full-width-1, half-width-0.5, no-line-break formula. The 100-point difference is accounted for by 50 points from ASCII weighting, 30 from half-width-space weighting, and 20 from excluding line breaks. If the rule is unspecified, keep both values unresolved rather than choosing one.
The passed result is that the raw total remained 1,080 after reopening a named copy and that its SHA-256 matched. The 980.0 value remains a local calculation. A matching product UI value, a matching external-service result, and the treatment of combining sequences or composite emoji remain unverified. Review the current Mac feature scope on the Rune Studio product page.
