Fix Issues with Local Image Links Containing Cyrillic Characters

[martyanovandrey]

Description
Address the problem where local image links with Cyrillic characters in filenames fail to resolve during document compilation. Currently, links like ![русские-символы](русские-символы.png) result in an error, as the encoding changes and the build process cannot locate the files.

Problem

• When linking images with Cyrillic names, the system encodes these characters, leading to file-not-found errors.
• Example error: ERR Asset not found: %D1%80%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B5-%D1%81%D0%B8%D0%BC%D0%B2%D0%BE%D0%BB%D1%8B.png in /whats-new.md.

Proposed Solution

• Implement a mechanism to properly handle and decode local image paths containing Cyrillic or non-ASCII characters during the build process.
• Ensure compatibility with both encoded and unencoded paths.

Benefits

• Enables the use of local images with Cyrillic filenames, broadening accessibility and usability for Russian and other non-ASCII languages.
• Improves user experience by preventing compilation errors related to asset paths.

Acceptance Criteria

• Local image links with Cyrillic characters in filenames resolve correctly, and relevant images are displayed without errors.
• Update documentation to include examples of using local image links with non-ASCII characters.
• Conduct testing to ensure reliable performance across various character sets.

Additional Notes

• Review the handling of filenames in different operating systems to ensure consistent behavior.
• Consider edge cases where filenames might contain mixed character sets or special symbols.

Entry point for development

transform/src/transform/plugins/links/collect.ts

Line 54 in 77d34db

const href = getHrefTokenAttr(linkToken);

transform/src/transform/utils.ts

Line 85 in 77d34db

export function getHrefTokenAttr(token: Token) {