Special Character & Sort order

[1ily]

I'm interested in using special characters and symbols to list collection categories next to each other. That way, the subgenres can be listed alongside the main genre.

What special characters does kobo accept and what order do they appear in?

I've noticed for the normal alphabet, it goes
!, ", #, $, %, ', (), *, +, ,, -, /, [Numbers], :, ;, <, =, >, ?, @, [Letters]

Periods go somewhere before *'s, ♡'s go somewhere after +'s but before letters, and the ☁︎ emoji works for some reason. Is there a list of all available symbols somewhere?

i.e.
.Fantasy
.Urban Fantasy
.Epic Fantasy

+Sci-fi
+Cyperpunk
+Space Opera

[JSWolf]

Originally Posted by 1ily

I'm interested in using special characters and symbols to list collection categories next to each other. That way, the subgenres can be listed alongside the main genre.

What special characters does kobo accept and what order do they appear in?

I've noticed for the normal alphabet, it goes
!, ", #, $, %, ', (), *, +, ,, -, /, [Numbers], :, ;, <, =, >, ?, @, [Letters]

Periods go somewhere before *'s, ♡'s go somewhere after +'s but before letters, and the ☁︎ emoji works for some reason. Is there a list of all available symbols somewhere?

i.e.
.Fantasy
.Urban Fantasy
.Epic Fantasy

+Sci-fi
+Cyperpunk
+Space Opera

Your sample are going to sort alphabetically. To have the order you want, you can put numbers after the symbols to keep the collections in order.
As to what symbols are allowed, I would think it doesn't matter as these collections names are not directory names but tags.
.01Fantasy
.02Urban Fantasy
.03Epic Fantasy

[Quoth]

I suspect less than what is possible in a Linux file name for Collection names.

[JSWolf]

Originally Posted by Quoth

I suspect less than what is possible in a Linux file name for Collection names.

I would think the only way to know for sure is to try it.

[Quoth]

Originally Posted by JSWolf

I would think the only way to know for sure is to try it.

Yes, due to abysmal product documentation of all ereaders. Unless someone can tell from the source (only some available) or binary.

With Kindle it also has to be compatible with Amazon's web site if you ever Sync.

[JSWolf]

Originally Posted by Quoth

Yes, due to abysmal product documentation of all ereaders. Unless someone can tell from the source (only some available) or binary.

With Kindle it also has to be compatible with Amazon's web site if you ever Sync.

Because I had 5 books to add to my Libra 2, I decided to do a collections test. I used ~ . * # + and they all worked. I'm thinking it may not matter what symbols are used as these are not directory names but tags.

[1ily]

Thanks for the input.
I did more manual testing as recommended and found these symbols will display:
〰️, [. * +], ~, ☁, ♠️, ♡, ♣️,♥️,♦️, [A-Z]

However, 〰️, ♠️,♣️,♥️,♦️ all have an empty [] square after it.

[JSWolf]

Originally Posted by 1ily

Thanks for the input.
I did more manual testing as recommended and found these symbols will display:
〰️, [. * +], ~, ☁, ♠️, ♡, ♣️,♥️,♦️, [A-Z]

However, 〰️, ♠️,♣️,♥️,♦️ all have an empty [] square after it.

Forget the brackets and just put text after these symbols.

[1ily]

Originally Posted by JSWolf

Forget the brackets and just put text after these symbols.

The character following the emoji are not actually brackets. it's the "unreadable character" square, but I can't be bothered to copy and paste it so people here can view it. The results are the same with text. See the attached images below. One is from the Kobo App and the other is from the KLC

[1ily]

Based on this website (https://www.camein.com/symbols-copy-paste.htm)
Here is a list of symbols that are compatible and appear on a KLC!

Do a direct copy and paste from the site so it copies over properly

✓,∞,★,☆,♥,♡,←,↓,→,♀,♂,ツ,✿,☂,☁,☼, ℃,℉,⚠,♨,☎,
☟,☝,☜,☞,♲,♪,♫,§,¶,«,»,[,],{,},—,–,¿,¡,‽,×,≠,¬,±,~,≈,÷,π,†,‡,€,$,¥,¢,£,ß,™,© ,®,@,½,²,★,☆,*,☀,⁂,⁑,⁂,⁑,✿,❀,♡,♥,♥️,♤,♡,♢,♧,♠,♥,♦, ♣,♩,♪,♫,♬,♭,♯,♮,∙,
▲,▼,◤,◢,◣,◥,△,▽,◁,▷,],▱,■,□,⊠,⊞,◆,◇,
█,▊,▋,▉,▇,▆,▅,▄,▃,
▢,◯,〇,⦿,⊗,⊕,◉,◎,◐,◑,◓,◒,●,○,◌,∞
√,∝,∇,∆,∅,−,±,∓,⧺,⧻,∥,∦,∫,∬,∭,∮,π,∑,∂,∀,∃,∈,∉,∋,∊, ∙,∘,
∪,∩,⊂,⊃,⊄,⊅,⊆,⊇∵,∴,≒,⊿,＝,×,⊠,⊞,⊗,⊕,⊥,
〈,〉,⌒,〄,〰️, [,.,*,+,], ~, ☁, ♠️,♡,♣️,♥️,♦️,!,@,#,$,%,^,&,*,(,),<,>,_,+,-,=,`,~,?,\,|,],},[,{,
⓪,①,②,③,④,⑤,⑥,⑦,⑧,⑨,⑩,⑪,⑫,⑬,⑭,⑮,⑯,⑰,⑱,⑲,⑳,
➀,➁,➂,➃,➄,➅,➆,➇,➈,➉,
⓿,❶,❷,❸,❹,❺,❻,❼,❽,❾,
⑴,⑵,⑶,⑷,⑸,⑹,⑺,⑻,⑼,⑽,⑾,⑿,⒀,⒁,⒂,⒃,⒄,⒅,⒆,⒇,
⒈,⒉,⒊,⒋,⒌,⒍,⒎,⒏,⒐,⒑,⒒,⒓,⒔,⒕,⒖,⒗,⒘,⒙,⒚,⒛,
⓵,⓶,⓷,⓸,⓹,⓺,⓻,⓼,⓽,⓾,
０,１,２,３,４,５,６,７,８,９,
Ⅰ,Ⅱ,Ⅲ,Ⅳ,Ⅴ,Ⅵ,Ⅶ,Ⅷ,Ⅸ,Ⅹ,Ⅺ,Ⅻ,Ⅿ,
ⅱ,ⅲ,ⅳ,ⅴ,ⅵ,ⅶ,ⅷ,ⅸ,ⅹ,ⅺ,ⅻ,ⅿ,
⁰,¹,²,³,⁴,⁵,⁶,⁷,⁸,⁹,
₀,₁,₂,₃,₄,₅,₆,₇,₈,₉,
ₐ,ₑ,ₒ,ₓ,ₔ,
⅟,½,⅓,⅔,¼,¾,⅕,⅗,⅘,⅙,⅚,⅛,⅜,⅝,⅞,%,‰,‱,
«,»,‹,›,¶,〈,〉,《,》,〔,〕,︵,︶,︷,︸,︽,︾,︹,︺,︿,﹀,<,>,＜,＞, {,},(,),｛,｝,（,）,‘,’,‛,‚,“,”,‟,„,·,•,‧,․,‥,…,′,″,‴, ‵,‶,‷,ʻ,ʼ,˜,～,＃,＆,＠,？,¿,¡,！,〝,―,—,–,‒,‑,†,‡,： ,；,*,/

[Quoth]

Though separate °C and °F using ° is better.

Some of these are regular punctuation ` ¬ ¦ | \ / !"£$%^&*()_-+={}[]:;@'~#<,>.
and easy on Linux altGr if not printed on the keyboard.« » ç “ ” ‘ ’ ẃẂ łŁ ðÐ þÞ § ß ŋ ħ Ħ ç Ç ĸ ¶ ® µ º

Others need the compose key ¢ ° ™ © ¥ ÷

[JSWolf]

Originally Posted by Quoth

Though separate °C and °F using ° is better.

Some of these are regular punctuation ` ¬ ¦ | \ / !"£$%^&*()_-+={}[]:;@'~#<,>.
and easy on Linux altGr if not printed on the keyboard.« » ç “ ” ‘ ’ ẃẂ łŁ ðÐ þÞ § ß ŋ ħ Ħ ç Ç ĸ ¶ ® µ º

Others need the compose key ¢ ° ™ © ¥ ÷

The thing to realize is that the filesystem has nothing to do with what characters can be displayed. These are not going to be part of a directory name. A collection is a tag. So what's allowed is up to the software as to what they allow. They can allow anything they want. They can even allow illegal filesystem characters.