Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement support for maintain server paths during editing and preview #3751

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

LeeHolmes
Copy link

@LeeHolmes LeeHolmes commented Jan 20, 2024

This PR addresses #3750

This change adds several features to make it easier to write Markdown articles that desire server-based paths (such as /images/my_image.png).

image image
  1. There is now a new preference page under images for "Maintaining server paths". You specify a server path (such as /images/) and a local path (such as c:\hugo\static\images), and Marktext will do the right mapping internally. Image previews will come from the images on your computer, while the content stored in the document will represent the corresponding server paths. Full documentation has been added to IMAGES.md.
  2. Path variables (like ${filename}) have been expanded to support year, month, and day. This helps prevent filename collisions and is common in many blogging platforms.
  3. Pasting images and dragging them into Marktext supports this path mapping as well, moving them to the local path as appropriate
  4. Image imports (pasting and or dragging) now retain the source image file name if possible, only using the image hash if there is a conflict. Images with names are easier to manage and show up appropriately in search engines
  5. The image edit dialog now has a 'Rename' tab so that you can rename the images to something more specific when they are just pasted from the clipboard. This simplifies the previous workflow that used to require editing the markdown and renaming the file in the filesystem manually.
image

There is also now a 'User Notification Dialog' component to let Marktext communicate with the user about error conditions.

image
Q A
Bug fix? No
New feature? Yes
Breaking changes? No
Deprecations? No
New tests added? Not needed, but existing tests pass
Fixed tickets Fixes #3750
License MIT

… articles that desire server-based paths (such as /images/my_image.png).

1) There is now a new preference page under images for "Maintaining server paths". You specify a server path (such as /images/) and a local path (such as c:\hugo\static\images), and
Marktext will do the right mapping internally. Image previews will come from the images on your computer, while the content stored in the document will represent the corresponding server paths.
Full documentation has been added to IMAGES.md.
2) Path variables (like ${filename}) have been expanded to support year, month, and day. This helps prevent filename collisions and is common in many blogging platforms.
3) Pasting images and dragging them into Marktext supports this path mapping as well, moving them to the local path as appropriate
4) Image imports (pasting and or dragging) now retain the source image file name if possible, only using the image hash if there is a conflict. Images with names are easier to manage and show up
appropriately in search engines
4) The image edit dialog now has a 'Rename' tab so that you can rename the images to something more specific when they are just pasted from the clipboard. This simplifies the previous workflow that
used to require editing the markdown and renaming the file in the filesystem manually.

There is also now a 'User Notification Dialog' component to let Marktext communicate with the user about error conditions.
@LeeHolmes
Copy link
Author

@Jocs et. all - this PR has been open for a while, anything I can do to help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support image paths that are different on the server than the local system
1 participant