Latin characters in calibre file names

[Cu6up5lk]

Yesterday I found a wonderful program Calibre and have already spent a lot of time copying books to the storage but suddenly noticed it translates all non-latin Russian characters in file names and folders to latin alphabet. Even taking in account the possibility to export books in native file names it still would create a lot of problems if I keep using the software professionally on my work.
I discovered the 11 years old thread with explanation of impossibility to use native filenames (like cyrillics):

https://www.mobileread.com/forums/sh...ad.php?t=99705

Maybe something finally changed after 11 years? Is there any way to enable native non-latin file names particularly for Windows? Maybe with the use of some plug-in... Anything?

[jhowell]

The information in this thread still applies:

Want to change folder structure or file names in the Calibre library?

[Cu6up5lk]

Originally Posted by jhowell

The information in this thread still applies:

Want to change folder structure or file names in the Calibre library?

Well, I don't have anything against folder structure of the Calibre program, I wish the header of opened file to be displayed with a correct caption in Windows OS at least. Currently it shows latinized version of the native book name in the windows caption that looks like a rubbish for a Russian eye. In hurry of work or at nervous situation it looks terribly confusing and annoying, especially for other people at my computer.
We live in 2021, the time when encoding is getting full of bearded women and pregnant men that are displayed correctly at any state. I don't believe it still not possible to store files with native names, especially when the Calibre program is able to export them right.

[Sarmat89]

If your reader shows the file name instead of the book title, it is broken or misconfigured.

[theducks]

Originally Posted by Sarmat89

If your reader shows the file name instead of the book title, it is broken or misconfigured.

or just really old and lame.

Calibre's View uses metadata, not filenames fore Book formats (I don't read the TXT source version, once in Calibre).

[Cu6up5lk]

Originally Posted by theducks

or just really old and lame.

Calibre's View uses metadata, not filenames fore Book formats (I don't read the TXT source version, once in Calibre).

I have to work with scanned documentation in pdf or even djvu file formats, often created in old times therefore having no modern metadata like files downloaded from fashionable book shops. In usual pdf viewers such file opens within one seconds while for built-in Calibre viewer it seems to be endless to open it. So it's okay for me to use Calibre for organization of scanned books storage while opening files with usual pdf programs.

I think the idea to rename non-English filenames to something unspeakable is just wrong.

[theducks]

Originally Posted by Cu6up5lk

I have to work with scanned documentation in pdf or even djvu file formats, often created in old times therefore having no modern metadata like files downloaded from fashionable book shops. In usual pdf viewers such file opens within one seconds while for built-in Calibre viewer it seems to be endless to open it. So it's okay for me to use Calibre for organization of scanned books storage while opening files with usual pdf programs.

I think the idea to rename non-English filenames to something unspeakable is just wrong.

Of course that is your opinion . (You are also free to not use a tool you dislike.)

But it differs from the Goal of the change: That is to work across as many OS (releases) and file systems as possible. Manyolder documents are still plagued with 'codepage' usage.
We learn to deal with old stuff every day.
5.25 (or 8") floppies. 78RPM records. Whitworth threads. ...

[BetterRed]

Originally Posted by Cu6up5lk

So it's okay for me to use Calibre for organization of scanned books storage while opening files with usual pdf programs.

Yep - I don't use the calibre-viewer as the designated viewer for any formats I retain (EPUB, CBZ, PDF, and DOCX).

If a format is unchecked in the Preferences->Behaviour->Use internal viewer for: list, calibre will use the default program as defined to the OS for the file type - e.g. PDF xChange for PDFs, Honeyview for CBZs, LO Writer for DOCX etc.

I use calibre's Open With to configure alternative viewers, e.g.the calibre viewer for EPUBs, MS Word for DOCX etc.

BR

[Cu6up5lk]

Originally Posted by theducks

Of course that is your opinion . (You are also free to not use a tool you dislike.)

Vise versa, I do actually like this tool! The only sort of "dislike" I have is about latin file names.

Originally Posted by theducks

But it differs from the Goal of the change: That is to work across as many OS (releases) and file systems as possible. Manyolder documents are still plagued with 'codepage' usage.
We learn to deal with old stuff every day.
5.25 (or 8") floppies. 78RPM records. Whitworth threads. ...

Yes, I realize it has to work on many platforms including out-dated and exotic one, probably my case is not very typical for global use too. Nevertheless I believe it's possible to fix the issue for Windows PC use only, it could be a checkbox in options for users like me not to use latin file names...

Originally Posted by BetterRed

Yep - I don't use the calibre-viewer as the designated viewer for any formats I retain (EPUB, CBZ, PDF, and DOCX).

Me too.

[Quoth]

Also when you export from Calibre (or copy to device) you can use a template to generate a filename from the title and author metadata, or other columns, which can be in Cyrillic, or anything your OS or reader supports. The default template can easily be edited.

Proper ereaders and ereading apps don't display the actual filename. Filenames can even be B01FYJDLHK_EBOK.azw4 or similar.

You don't need to change how files are referenced in the Calibre library, nor should you.

[BetterRed]

Originally Posted by Cu6up5lk

…

Yes, I realize it has to work on many platforms including out-dated and exotic one, probably my case is not very typical for global use too. Nevertheless I believe it's possible to fix the issue for Windows PC use only, it could be a checkbox in options for users like me not to use latin file names...

Calibre is open source, so you could download the code and create a private fork by applying the fix that you believe is possible.

BR

[Cu6up5lk]

Originally Posted by BetterRed

Calibre is open source, so you could download the code and create a private fork by applying the fix that you believe is possible.

BR

I'm thinking about this idea since I found out Calibre is written mainly with Python language and I have some basic knowledge of Python. I still have not researched the code and not figured out which part of code is responsible for file storage. Probably this is the only solution for me.