Individual fonts to a file name
Individual fonts to a file name
I received a file with a weird decorated and bold font.
Searching the net, nothing.
I discovered that using charmap it is possible (win10) to name a file even with the most unexpected fonts and symbols.
Colorize fonts, background, age, etc. Why not change the fonts itself, like
using a different font to name specific words like "setup" or changing the font for .lnk files, etc.
Just an idea.
Searching the net, nothing.
I discovered that using charmap it is possible (win10) to name a file even with the most unexpected fonts and symbols.
Colorize fonts, background, age, etc. Why not change the fonts itself, like
using a different font to name specific words like "setup" or changing the font for .lnk files, etc.
Just an idea.
-
- Site Admin
- Posts: 63404
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Individual fonts to a file name
Interesting. Could you attach such a file (zipped) to a post here?
FAQ | XY News RSS | XY Bluesky
Re: Individual fonts to a file name
Well... Stuff like colouring parts of filenames (differing from changing the entire filename, we already can do that; based on RegEx, mostly) would be intriguing to me, too.
Not sure about different fonts, though.
Not sure about different fonts, though.
Re: Individual fonts to a file name
Sorry, the file is gone.
I myself could insert symbols, but couldn't change the font itself.
Maybe, who did it, modified a normal Windows font by changing the symbols to a draw of letters. It would be a wearisome job.
I remember that something like this was possible with the ancient Windows 98, typing right Alt + number pad numbers.
I really don't know how, but he (?) did it.
Using the font "Segoe MDL2 Assets" Unicode, all letters change to weird symbols.
He (?) modified this one? I don't know.
- Attachments
-
- ¹شßњ⓴Ð◆.zip
- (251 Bytes) Downloaded 51 times
-
- Site Admin
- Posts: 63404
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Individual fonts to a file name
These are just Unicode characters of one font. No font change involved. Nothing new.
FAQ | XY News RSS | XY Bluesky
Re: Individual fonts to a file name
AHA! I found it in the internet.
I don't know how they do it.
𝕿𝖍𝖎𝖘 𝖎𝖘 𝖆 𝖋𝖔𝖓𝖙
File zipped and attached (0 bytes)
from
lingojam.com/TextFonts
There are some problems. Not all the text editors shows this font. Some shows ?????????????.txt
Seems that the forum considered the zip file with this font an "http error"
I don't know how they do it.
𝕿𝖍𝖎𝖘 𝖎𝖘 𝖆 𝖋𝖔𝖓𝖙
File zipped and attached (0 bytes)
from
lingojam.com/TextFonts
There are some problems. Not all the text editors shows this font. Some shows ?????????????.txt
Seems that the forum considered the zip file with this font an "http error"
- Attachments
-
- Flile.zip
- (236 Bytes) Downloaded 53 times
Re: Individual fonts to a file name
Who would've thought it was even possible to use fonts other than the system-defined one? I downloaded the file to see what happens. In Windows Notepad and Wordpad, the title bar shows the font. In Notepad++, the title bar shows ???????????.txt but the file tab shows the font.
Windows 10 Pro 22H2
-
- Site Admin
- Posts: 63404
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Individual fonts to a file name
The XY character table tells you something about it:
So, these characters are extensions of the 16-bit Unicode set. It's not a different font, but fixed characters in the extended set.
Code: Select all
# char dec hex utf8 utf8hex remark
1 55349 D835 High Surrogate
𝕿 56703 DD7F ð•¿ F0 9D 95 BF Low Surrogate
2 55349 D835 High Surrogate
𝖍 56717 DD8D ð– F0 9D 96 8D Low Surrogate
3 55349 D835 High Surrogate
𝖎 56718 DD8E ð–Ž F0 9D 96 8E Low Surrogate
4 55349 D835 High Surrogate
𝖘 56728 DD98 ð–˜ F0 9D 96 98 Low Surrogate
5 32 20 20
6 55349 D835 High Surrogate
𝖎 56718 DD8E ð–Ž F0 9D 96 8E Low Surrogate
7 55349 D835 High Surrogate
𝖘 56728 DD98 ð–˜ F0 9D 96 98 Low Surrogate
8 32 20 20
9 55349 D835 High Surrogate
𝖆 56710 DD86 ð–† F0 9D 96 86 Low Surrogate
10 32 20 20
11 55349 D835 High Surrogate
𝖋 56715 DD8B ð–‹ F0 9D 96 8B Low Surrogate
12 55349 D835 High Surrogate
𝖔 56724 DD94 ð–” F0 9D 96 94 Low Surrogate
13 55349 D835 High Surrogate
𝖓 56723 DD93 ð–“ F0 9D 96 93 Low Surrogate
14 55349 D835 High Surrogate
𝖙 56729 DD99 ð–™ F0 9D 96 99 Low Surrogate
FAQ | XY News RSS | XY Bluesky
Re: Individual fonts to a file name
OK: other view, but fiits here in the moment
XY seems to work well with such characters on fiilenames, text, etc.
But it badly fails with scripting...
Here XY interprets characters as 2-bytes. In real they are UTF-16, i.e *most* used chars can be expressed by 2 bytes, but much seldom used chars are 2*(2Bytes)! And '𝕿' is one of those...
The "directest" interfaces here are asc() and chr() - both don't understand this. (asc() i.e uses the number modulo x'10000'), chr() seems to only interpret the first 2 bytes.
(OK: there are more problems like substring: '𝕿' is 1 char, but 2*2bytes - at least it must be defined what happens...)
By the way: the name asc is very out of time: ascii is *only* 7-Bit! 8bit is something like ansi - language-dependent. Unicode is the full representation of 3 bytes (U+0000 - U+10FFFF), WIN-internal is UTF-16.
OK Don - what's to expect with these problems?
EDIT: correct definition of unicode
XY seems to work well with such characters on fiilenames, text, etc.
But it badly fails with scripting...
Here XY interprets characters as 2-bytes. In real they are UTF-16, i.e *most* used chars can be expressed by 2 bytes, but much seldom used chars are 2*(2Bytes)! And '𝕿' is one of those...
The "directest" interfaces here are asc() and chr() - both don't understand this. (asc() i.e uses the number modulo x'10000'), chr() seems to only interpret the first 2 bytes.
(OK: there are more problems like substring: '𝕿' is 1 char, but 2*2bytes - at least it must be defined what happens...)
By the way: the name asc is very out of time: ascii is *only* 7-Bit! 8bit is something like ansi - language-dependent. Unicode is the full representation of 3 bytes (U+0000 - U+10FFFF), WIN-internal is UTF-16.
OK Don - what's to expect with these problems?
EDIT: correct definition of unicode
Win11 Pro 23H2 Gerrman
-
- Site Admin
- Posts: 63404
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Individual fonts to a file name
chr() will work in next beta. The rest after TB.
FAQ | XY News RSS | XY Bluesky
Re: Individual fonts to a file name
OK: saw your enhancement of chr(): very helpful
Especially that you can directly set the U+nnnn as chr(0xnnnn)! I.e. in this means we don't see the rules of UTF-16!
Now *every* try of asc() on such a "char" must fail - it will interpret the high surrogate as a full character.
As chr() defines that it will work on (only) one char, you could enhance it: test 2 bytes for a high surrogate, and if it is interpret 2*2 bytes (i.e. high and low surrogate) as a char.
1) yes: easy said
2) *can* be wrong - but not doing it *must* be wrong
I agree: strlen(), substr(), etc should wait...
... as you often said: needs more thinking!



Especially that you can directly set the U+nnnn as chr(0xnnnn)! I.e. in this means we don't see the rules of UTF-16!
Now *every* try of asc() on such a "char" must fail - it will interpret the high surrogate as a full character.
As chr() defines that it will work on (only) one char, you could enhance it: test 2 bytes for a high surrogate, and if it is interpret 2*2 bytes (i.e. high and low surrogate) as a char.
1) yes: easy said
2) *can* be wrong - but not doing it *must* be wrong
I agree: strlen(), substr(), etc should wait...
... as you often said: needs more thinking!
Win11 Pro 23H2 Gerrman
-
- Site Admin
- Posts: 63404
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Individual fonts to a file name
I had to do it, because there were old bugs in asc(). Next beta. 

FAQ | XY News RSS | XY Bluesky
Re: Individual fonts to a file name
Had a look at the curr beta
More than I thought I could ask for

(Maybe I should have asked some years ago, when I played with some exotic codepoints...
I love to use these as separators for lists of tokens: no risk a token contains them
)

More than I thought I could ask for



(Maybe I should have asked some years ago, when I played with some exotic codepoints...
I love to use these as separators for lists of tokens: no risk a token contains them

Win11 Pro 23H2 Gerrman