slack-markdown-parser 2.2.4__tar.gz → 2.2.5__tar.gz

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/CHANGELOG.md

@@ -6,6 +6,12 @@ The format is based on Keep a Changelog, and the project follows Semantic Versio
 
 ## [Unreleased]
 
+## [2.2.5] - 2026-03-14
+
+### Fixed
+
+- Preserved raw English-like emphasis when it only touches surrounding punctuation, avoiding unnecessary ZWSP around cases such as `**APIYI (apiyi.com)**:` that Slack already renders correctly on its own.
+
 ## [2.2.4] - 2026-03-11
 
 ### Changed

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: slack-markdown-parser
-Version: 2.2.4
+Version: 2.2.5
 Summary: Convert LLM Markdown into Slack Block Kit markdown/table messages
 Author: darkgaldragon
 License-Expression: MIT
@@ -61,7 +61,7 @@ If Slack itself does not support a construct in `markdown` blocks, this library
 - Repair common LLM table issues such as missing outer pipes, missing separator rows, mismatched column counts, and empty cells
 - Split output into multiple Slack messages when needed to satisfy Slack's "one table per message" constraint
 - Sanitize ANSI/control characters and neutralize invalid Slack angle-bracket tokens before block generation
-- Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks
+- Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks, while preserving English-like punctuation-only boundaries that Slack already renders reliably
 - Use locale-aware visible-space padding for nested inline-code emphasis in dense Japanese, Chinese, and Korean text when Slack requires stronger boundaries than ZWSP alone
 - Support Markdown and Slack-style links inside table cells
 - Build fallback text for `chat.postMessage.text` from generated blocks, normalizing synthetic ZWSP and any parser-inserted visible-space padding used only for rendering stability

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/README-ja.md

@@ -30,7 +30,7 @@ Slack の `markdown` ブロック自体が対応していない構文は、古
 - LLM が生成する多様な Markdown テーブルで起こり得る記法の揺れ（外枠パイプ不足、セパレータ行不足、列数不一致、空セル）を検知し自動補完。Slack `table` ブロックの `invalid_blocks` エラーを未然に回避
 - テーブルごとにメッセージを自動分割（Slack の「1メッセージ1テーブル」制約に対応）
 - ANSI escape / 制御文字を除去し、不正な Slack 角括弧トークンを自動で無害化
-- 装飾記号の前後に ZWSP を付与して表示崩れを抑制（フェンスドコードブロック内は除外、インラインコードは付与対象）
+- 装飾記号の前後に ZWSP を付与して表示崩れを抑制（フェンスドコードブロック内は除外、インラインコードは付与対象）。ただし英語系で周囲が句読点だけのケースは、Slack がそのまま安定描画できる場合に ZWSP を増やさない
 - 日本語・中国語・韓国語の密着文脈で、インラインコードを内包する装飾には可視スペースを補って Slack 表示を安定化
 - テーブルセル内の Markdown link / Slack link を認識
 - `chat.postMessage.text` 用の fallback テキストを生成（表示安定化のために入れた ZWSP や人工的な可視スペースは通知文では自然な形に正規化）

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/README.md

@@ -30,7 +30,7 @@ If Slack itself does not support a construct in `markdown` blocks, this library
 - Repair common LLM table issues such as missing outer pipes, missing separator rows, mismatched column counts, and empty cells
 - Split output into multiple Slack messages when needed to satisfy Slack's "one table per message" constraint
 - Sanitize ANSI/control characters and neutralize invalid Slack angle-bracket tokens before block generation
-- Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks
+- Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks, while preserving English-like punctuation-only boundaries that Slack already renders reliably
 - Use locale-aware visible-space padding for nested inline-code emphasis in dense Japanese, Chinese, and Korean text when Slack requires stronger boundaries than ZWSP alone
 - Support Markdown and Slack-style links inside table cells
 - Build fallback text for `chat.postMessage.text` from generated blocks, normalizing synthetic ZWSP and any parser-inserted visible-space padding used only for rendering stability

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/docs/spec-ja.md

@@ -145,13 +145,17 @@ LLM は外枠パイプの省略、セパレータ行の欠落、列数の不一
 
 ### 対象パターン
 
-以下の装飾記号について、前後のどちらか一方でも隣接文字がスペース・タブ・改行・ZWSP でない場合、または行頭・行末に接している場合、装飾トークン全体を ZWSP（U+200B）で囲って Slack に独立した境界として認識させる:
+以下の装飾記号について、前後のどちらか一方でも隣接文字がスペース・タブ・改行・ZWSP でない場合、または行頭・行末に接している場合、通常は装飾トークン全体を ZWSP（U+200B）で囲って Slack に独立した境界として認識させる:
 
 - `` `code` `` — インラインコード
 - `**bold**` — 太字
 - `*italic*` — 斜体
 - `~~strike~~` — 取消線
 
+例外:
+
+- 装飾の中身が英語系テキストで、密着している隣接文字が句読点だけの場合は、元のトークンをそのまま維持する。`**APIYI (apiyi.com)**:` のように Slack が素のままで安定描画できるケースで、過剰な ZWSP を入れないため。
+
 ### 除外範囲
 
 - **フェンスドコードブロック**（`` ``` ... ``` `` および `~~~ ... ~~~`）内は一切変更しない

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/docs/spec.md

@@ -144,13 +144,17 @@ In languages such as Japanese that do not use spaces between words, formatting m
 
 ### Target patterns
 
-For each formatting token below, if either adjacent side is not a space, tab, newline, or existing ZWSP, or if the token touches the start or end of a line, the whole token is wrapped in ZWSP (`U+200B`) so Slack recognizes it as a standalone formatting boundary:
+For each formatting token below, if either adjacent side is not a space, tab, newline, or existing ZWSP, or if the token touches the start or end of a line, the whole token is normally wrapped in ZWSP (`U+200B`) so Slack recognizes it as a standalone formatting boundary:
 
 - `` `code` ``: inline code
 - `**bold**`: bold
 - `*italic*`: italic
 - `~~strike~~`: strikethrough
 
+Exception:
+
+- If the token body is English-like text and the only tight neighbors are punctuation characters, the raw token is preserved. This avoids over-correcting spans such as `**APIYI (apiyi.com)**:` that Slack already renders correctly without extra ZWSP.
+
 ### Excluded regions
 
 - Fenced code blocks (both `` ``` ... ``` `` and `~~~ ... ~~~`) are never modified

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "slack-markdown-parser"
-version = "2.2.4"
+version = "2.2.5"
 description = "Convert LLM Markdown into Slack Block Kit markdown/table messages"
 readme = "README.md"
 requires-python = ">=3.10"

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/slack_markdown_parser/__init__.py

@@ -1,6 +1,6 @@
 """slack-markdown-parser public package API."""
 
-__version__ = "2.2.4"
+__version__ = "2.2.5"
 __license__ = "MIT"
 
 from .converter import (

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/slack_markdown_parser/converter.py

@@ -199,6 +199,52 @@ def _find_inline_code_span_end(text: str, start: int) -> int | None:
     return closing + len(delimiter)
 
 
+def _is_punctuation_like(char: str, boundary_chars: set[str]) -> bool:
+    return bool(char) and char not in boundary_chars and not char.isalnum()
+
+
+def _should_preserve_raw_punctuation_emphasis(
+    source: str,
+    start: int,
+    end: int,
+    token_text: str,
+    boundary_chars: set[str],
+) -> bool:
+    tight_chars = []
+    before_char = source[start - 1] if start > 0 else ""
+    after_char = source[end] if end < len(source) else ""
+
+    if before_char and before_char not in boundary_chars:
+        tight_chars.append(before_char)
+    if after_char and after_char not in boundary_chars:
+        tight_chars.append(after_char)
+
+    if not tight_chars:
+        return False
+    if any(not _is_punctuation_like(char, boundary_chars) for char in tight_chars):
+        return False
+    if any(_is_han_or_kana_char(char) or _is_hangul_char(char) for char in token_text):
+        return False
+
+    left_idx = start - 1
+    while left_idx >= 0 and source[left_idx] in boundary_chars:
+        left_idx -= 1
+    if left_idx >= 0 and (
+        _is_han_or_kana_char(source[left_idx]) or _is_hangul_char(source[left_idx])
+    ):
+        return False
+
+    right_idx = end
+    while right_idx < len(source) and source[right_idx] in boundary_chars:
+        right_idx += 1
+    if right_idx < len(source) and (
+        _is_han_or_kana_char(source[right_idx]) or _is_hangul_char(source[right_idx])
+    ):
+        return False
+
+    return True
+
+
 def normalize_bare_urls_for_slack_markdown(text: str) -> str:
     """Wrap bare URLs in autolink syntax for stable Slack markdown rendering."""
     if not text:
@@ -369,6 +415,10 @@ def _format_markdown_with_spacing_metadata(text: str) -> tuple[str, List[int]]:
         after_safe = end < len(source) and source[end] in boundary_chars
         if before_safe and after_safe:
             return match.group(0)
+        if _should_preserve_raw_punctuation_emphasis(
+            source, start, end, match.group(0), boundary_chars
+        ):
+            return match.group(0)
 
         # When either outer edge is tightly coupled to surrounding text or
         # punctuation, wrap the whole token so Slack can treat the decoration

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/slack_markdown_parser.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: slack-markdown-parser
-Version: 2.2.4
+Version: 2.2.5
 Summary: Convert LLM Markdown into Slack Block Kit markdown/table messages
 Author: darkgaldragon
 License-Expression: MIT
@@ -61,7 +61,7 @@ If Slack itself does not support a construct in `markdown` blocks, this library
 - Repair common LLM table issues such as missing outer pipes, missing separator rows, mismatched column counts, and empty cells
 - Split output into multiple Slack messages when needed to satisfy Slack's "one table per message" constraint
 - Sanitize ANSI/control characters and neutralize invalid Slack angle-bracket tokens before block generation
-- Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks
+- Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks, while preserving English-like punctuation-only boundaries that Slack already renders reliably
 - Use locale-aware visible-space padding for nested inline-code emphasis in dense Japanese, Chinese, and Korean text when Slack requires stronger boundaries than ZWSP alone
 - Support Markdown and Slack-style links inside table cells
 - Build fallback text for `chat.postMessage.text` from generated blocks, normalizing synthetic ZWSP and any parser-inserted visible-space padding used only for rendering stability

{slack_markdown_parser-2.2.4 → slack_markdown_parser-2.2.5}/tests/test_converter.py

@@ -361,6 +361,20 @@ def test_bold_with_tight_boundary_on_left_is_wrapped_on_both_sides() -> None:
     )
 
 
+def test_english_bold_with_punctuation_on_right_stays_raw() -> None:
+    text = "• **APIYI (apiyi.com)**: OpenAI互換"
+    converted = add_zero_width_spaces_to_markdown(text)
+
+    assert converted == text
+
+
+def test_english_bold_with_japanese_period_stays_raw() -> None:
+    text = "• **APIYI (apiyi.com)**。"
+    converted = add_zero_width_spaces_to_markdown(text)
+
+    assert converted == text
+
+
 def test_blocks_to_plain_text_and_fallback_generation() -> None:
     raw = """# Title