Using your solution to generate website with Obsidian Zola. Can I somehow override the

It's currently pretty hard-coded: <div cla

Related issue: <a class="issue-link js-issue-link" data-error-text="Failed to load tit

Can I replace spaces with dashes for URL generation? about obsidian-export HOT 4 OPEN

assopri commented on June 5, 2024 4

Can I replace spaces with dashes for URL generation?

from obsidian-export.

Comments (4)

zoni commented on June 5, 2024 1

It's currently pretty hard-coded:

obsidian-export/src/lib.rs

Lines 674 to 688 in 6af4c91

    
           let target_file = target_file.unwrap(); 
        
           // We use root_file() rather than current_file() here to make sure links are always 
        
           // relative to the outer-most note, which is the note which this content is inserted into 
        
           // in case of embedded notes. 
        
           let rel_link = diff_paths( 
        
               target_file, 
        
               &context 
        
                   .root_file() 
        
                   .parent() 
        
                   .expect("obsidian content files should always have a parent"), 
        
           ) 
        
           .expect("should be able to build relative path when target file is found in vault"); 
        
           let rel_link = rel_link.to_string_lossy(); 
        
           let mut link = utf8_percent_encode(&rel_link, PERCENTENCODE_CHARS).to_string();

I'm not against making this more configurable/overrideable, but it would be nice to know what you're trying to achieve and why you would want a different behavior.

The intent of obsidian-export is to give you a normalized CommonMark input to feed to later processors (such as static site generators like Zola). It's obsidian-export's job to make sure that input has valid links/paths on the local filesystem that those tools can resolve correctly (which it currently does).

It's not intended to construct final URLs directly, as that's really the job of Hugo, Zola, etc. to do (because it's also their concern to change .md to .html, or to link to a directory instead of a file in case of "pretty URLs")

from obsidian-export.

benbohmer commented on June 5, 2024

This would be useful for many use cases, not only Zola!

from obsidian-export.

zoni commented on June 5, 2024

Related issue: #73

from obsidian-export.

smaroukis commented on June 5, 2024

I also had an issue where I wanted to leave the spaces encoded as literal spaces, for a responsive image partial for a hugo site, which uses the image in markdown as

{{< imgh src="filename with spaces.png" alt="alt-text" >}}

(since the image filename itself is not renamed to be percent encoded by obsidian-export the partial does not find the asset)

Of course the partial could be changed to first percent encode the resource, but I'm just getting started with hugo...

Partial I'm using: https://mijndertstuij.nl/posts/hugo-responsive-images/

from obsidian-export.

Recommend Projects

Can I replace spaces with dashes for URL generation? about obsidian-export HOT 4 OPEN

Comments (4)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	let target_file = target_file.unwrap();
	// We use root_file() rather than current_file() here to make sure links are always
	// relative to the outer-most note, which is the note which this content is inserted into
	// in case of embedded notes.
	let rel_link = diff_paths(
	target_file,
	&context
	.root_file()
	.parent()
	.expect("obsidian content files should always have a parent"),
	)
	.expect("should be able to build relative path when target file is found in vault");

	let rel_link = rel_link.to_string_lossy();
	let mut link = utf8_percent_encode(&rel_link, PERCENTENCODE_CHARS).to_string();