# iCouldPlay ASS shearing: fax and fay are not font italics or rotation

Language: en
Canonical: [iCouldPlay ASS shearing: fax and fay are not font italics or rotation](<https://allluckly.cn/en/guides/icouldplay-ass-fax-fay-shear-not-font-italic-or-rotation/>)
中文：[中文 HTML](<https://allluckly.cn/guides/icouldplay-ass-fax-fay-shear-not-font-italic-or-rotation/>)
English: [English HTML](<https://allluckly.cn/en/guides/icouldplay-ass-fax-fay-shear-not-font-italic-or-rotation/>)
Published: 2026-11-18T00:00:00+08:00
Modified: 2026-11-18T09:24:31+08:00
Author: Bison

Compare horizontal and vertical shear tags on identical AB12 text, retaining an undeformed reference and a separate geometric model.

English translation of the [Chinese original](<https://allluckly.cn/guides/icouldplay-ass-fax-fay-shear-not-font-italic-or-rotation/>), translated on 2026-11-18. Original publication dates, attribution, code and version notes are retained.

Slanted subtitles may arise from font italics, rotation or shearing; appearance alone does not identify one cause. Prepare three ASS override excerpts externally and observe them through an actually supported iCouldPlay subtitle path. Keep the mathematical illustration separate from real glyph pixels; the player is not a subtitle editor or geometry solver.

## Fix the clip, text and readable style

Use an owned ten-second still-scene clip and an already readable ASS practice copy, fixing a640×360 script canvas and available Default style. Display AB12 three times without changing sentence, size, weight or font, which would confound glyph widths. Retain the style original and edit externally; iCouldPlay is not assumed to enter overrides. Renaming an SRT does not create legal ASS: obtain a valid header and format first. Do not crop or rotate the video for this subtitle transformation.

## Assign three nonoverlapping conditions

Place no shear, fax0.25 and fay0.25 at1–3 s,3–5 s and5–7 s, each lasting two seconds. Share the centred anchor and position, explicitly controlling rotation 0, italics 0 and scale 100. Dialogue fields supply absolute times;0.25 is a dimensionless shear factor, not a quarter-second duration. Keep expected tags, observed glyphs and unknowns in separate columns. A screenshot at the3 s boundary does not establish inspection of both intervals.

## Insert the excerpts into an existing valid ASS

The following Dialogue lines match a common event Format and need an existing Script Info, V4+ Styles and Events header; they are not a complete subtitle file alone. Check the practice Format’s Layer, Start, End, Style and remaining order before replacing events, adapting to the real header when necessary. Both fax and fay are explicit on each line so prior settings are not mistaken for defaults. Braces contain instructions and AB12 is text. If literal tags appear, check parsing before comparing slant.

```text
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: 0,0:00:01.00,0:00:03.00,Default,,0,0,0,,{\an5\pos(320,180)\frz0\i0\fscx100\fscy100\fax0\fay0}AB12
Dialogue: 0,0:00:03.00,0:00:05.00,Default,,0,0,0,,{\an5\pos(320,180)\frz0\i0\fscx100\fscy100\fax0.25\fay0}AB12
Dialogue: 0,0:00:05.00,0:00:07.00,Default,,0,0,0,,{\an5\pos(320,180)\frz0\i0\fscx100\fscy100\fax0\fay0.25}AB12
```

## Separate tag factors from the geometric illustration

Aegisub defines zero as no shearing and fax/fay as the two directions. Separately stipulate paper maps H(x,y)=(x+0.25y,y) and V(x,y)=(x,y+0.25x): point(40,20) becomes(45,20) or(40,30). Those explicitly defined mathematical coordinates are not actual font pixels in iCouldPlay; glyph coordinates, anchors and rendering scale add conditions. Draw reference axes and retain the origin, then record actual direction instead of treating paper values as measurements.

## Use italics and rotation as separate counterexamples

On separate copies change only i0 to i1 with both shears zero, or only frz to ten degrees. These test italics and rotation without merging them into the original three conditions. Italics can select different glyphs and need not match shear 0.25; rotation changes overall orientation rather than shearing one axis. The documentation places shearing after rotation and says its coordinate system is unaffected by org. This exercise fixes rotation 0 rather than assuming complex combinations commute. Observe only counterexample versions actually produced.

## Check subtitle identity before appearance during playback

Associate the complete owned ASS with the same video through a subtitle path actually supported by the installation. Verify AB12, interval timing and absence of a second overlaid subtitle first. Observe inside each interval rather than exactly at transitions. Keep display mode, size overrides and orientation fixed or record uncontrolled conditions. Record observed shear differences, no difference or parsing failure as seen. External-editor rendering does not certify iCouldPlay, and public subtitle support does not guarantee identical ASS overrides across every engine.

## Troubleshoot parsing, overrides and clipping in order

For literal directives check ASS structure and event Format. If all conditions slant, inspect Default italics, stale files and other tags. Missing glyph portions after deformation require checking frame edges before calling characters deleted. Change one failure-copy factor and retain the normal first interval rather than changing font, rotation and weight together. Separate readability from whether a tag affects rendering: strong distortion can work yet be unreadable. The documented typical factors are small;0.25 is a modest comparison, not an extreme compatibility test.

## Reopen with the three-condition comparison and limits

Save complete legal ASS, the three literal excerpts, external H/V point values and actual observations. Reopen the original video and verify subtitle identity again. Identify the fax-only and fay-only conditions and explain why i1 and frz10 are different variables. Retain video direction/content and edit only owned subtitle copies. Leave unperformed association or counterexamples pending. Claim neither measured font pixels from paper points, an automatic iCouldPlay shear editor, nor universal fonts, script sizes and output-device compatibility from one result.

## Related tutorials and sources

[iCouldPlay ASS rotation origin: separate the anchor from the pivot](<https://allluckly.cn/en/guides/icouldplay-ass-rotation-origin-position-anchor-quarter-turn/>); [iCouldPlay ASS positioning: separate script coordinates, anchors and device pixels](<https://allluckly.cn/en/guides/icouldplay-ass-pos-script-coordinate-display-pixels/>).

Method sources: [Aegisub ASS tags: text shearing, rotation and italics](<https://aegisub.org/docs/latest/ass_tags/>).

Checked on 18 November 2026: the [official iCouldPlay listing](<https://apps.apple.com/cn/app/id6755653178>) and [Apple public lookup](<https://itunes.apple.com/lookup?id=6755653178&country=cn&entity=software&timestamp=20261118-hls>) list version 1.1.1, requiring iOS / iPadOS 15.0 or later. Prepare text and calculations externally; iCouldPlay selects and observes existing owned real sources through actually visible installed controls. Placeholder addresses supply neither media nor keys. Keep syntax, hypothetical calculations, real-byte evidence and viewing separate, marking unperformed steps accordingly. No exhaustive physical-device, private-server, engine or output-device compatibility testing is claimed.

