Quote:
Originally Posted by Latios
...So, I still dont understand how calibre DOES allow this (in blue) :
Hope, Jens R_ Water..2000
(this is a real example)
But it DOES NOT allows this (in red) :
Hope, Jens R.. Water.. 2000...
|
What you see as 2 periods in your blue example is interpreted as the first being a period as part of the filename and the second being the extension separator - so interpreted in the filename as being one period.
While two periods are allowed within filenames (as in your red example) by Windows (and I think by Linux too) I have never seen them so used and I suspect most people would do a double take if seen used by others; that if only because use of the second period normally adds nothing to the clarity of a filename (and, in Windows, it uses up one of the 260 path length characters total path and filename length for no purpose). A single period (and spaces) may add to the clarity of the filename (such as an author's name e.g. R. L. Stevenson)
Many people regard it as bad practice to use any periods (or spaces) at all other than for the extension separator. As far as Windows users go this is a likely mainly a hangover from original DOS file naming days. Also as theducks has pointed out single and double periods have a specific use when preceded by a \ (or/).
For myself I use the gamut of Windows allowed characters when naming files but I would not use double periods. When using spaces I normally consider whether their use may cause problems (e.g. a human typing a filename can accidently strike two spaces and not notice it - two spaces are allowed in Windows) in which case I use a Low Line instead.