The prettifier unprettifies a `table`.

[RokeJulianLockhart]

When filing github/markup/issues/1168#issuecomment-4313570361, I realised that the undermentioned, when prettified:

| Syntax              | Example   | Expected behavior | Actual behavior  |
|---------------------|-----------|-------------------|------------------|
| `@github`           | @github   | mention link      | mention link     |
| `\@github`          | \@github  | no mention link   | **mention link** |
| ``` `@github` ```   | `@github` | no mention link   | no mention link  |
| `@​github` with ZWSP | @​github   | no mention link   | no mention link  |

…becomes:

| Syntax               | Example   | Expected behavior | Actual behavior  |
|----------------------|-----------|-------------------|------------------|
| `@github`            | @github   | mention link      | mention link     |
| `\@github`           | \@github  | no mention link   | **mention link** |
| ``` `@github` ```    | `@github` | no mention link   | no mention link  |
| `@​github` with ZWSP | @​github  | no mention link   | no mention link  |

My Environment

Version: 4.0.0
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=darkriszty.markdown-table-prettify

[darkriszty]

Thanks for filing this, I haven't considered zero width characters yet, but it is an easy change.

[RokeJulianLockhart]

@darkriszty, in retrospect, there is always a possibility that the font in use might render ZWCs, however. Perhaps, it should be controlled by a preference?

[darkriszty]

Thanks for the suggestion. The merged fix for #107 should be OK for the majority of cases, since these characters are defined as zero-width and most normal monospaced font should render them invisibly.
The core logic uses a best-effort implementation (0 for ZWCs, 2 for CJK, 1 for everything else) that matches standard monospaced fonts.

But this ties into the broader character width challenge. A more comprehensive solution could involve font-specific character width profile configurations with sensible defaults which are user configurable too (reading the font family and applying per-character width rules), but the configuration complexity and maintenance burden would be significant for both users and/or the project, and it's unlikely anyone would really change it from the defaults. If there would be a big enough demand, this could be explored in #4

[darkriszty]

Included in v4.1.0