Inspiring

Answered

Error when saving as version control

Forum|Forum|3 years ago
September 21, 2022
4 replies
444 views

Latest ID

used for many years no problem

I save numerous files with version control

e,g, MDC_dyslipidaemia_v1.0, MDC_dyslipidaemia_v1.1, MDC_dyslipidaemia_v1.2

note v1.0, v1.1....etc

suddenly when i save a file with an incremental number, ID stops recognising it as a file name, instead recognises it as a file extension i.e. a .1 file (dot one file)

for 6 years this has not been a problem. it suddenly started. i have not changed or done anything differently

Any help appercaited

sean

This topic has been closed for replies.

Correct answer Sean5CF1

The problem is that even after you find the culprit in this case, and fix it (assuming you manage to get it fixed), it may crop up at any time again in the future. The reason for this is, as I understand it, that you are relying on the programmers to not be lazy in the way they parse filename/extensions. The vast majority of frameworks (eg, built in OS frameworks talking to the filesystem) will get this right, but there will be cases where the programmer takes a shortcut and quickly matches the first dot as the delimiter, because it is more work to match the file extension correctly. So, even if you get it fixed this time, you are only fixing it this time. It will come again.

It certainly isn't correct to call the system you describe "THE common file evolution standard". I would call it "THE most common file naming mistake". I was reluctant to give it up back in the day, but the peace of mind has been well worth it, and I've lost nothing. Actually, the system I use now is superior anyway because two-alpha-characters better convey the phase of the document (as in your system 1=pre-draft, whereas mine is DR).

Anyway, some food for thought if nothing else. Hope you get it fixed and all the best.

- Mark

Thanks Mark, appreciated

OK solved.

I reread Bobs post and what i mistook as file extension, i was attributing to file "type"

i clicked on file name extentions and noted .indd was missing

Of course i added .indd extension to the file and tah dah

As you were Support peeps - a simple fix, but still not sure why it happened. And only with v1.1

Meh, as long as this is all it takes to fix, i can live with it

thank you all - highly appreciated

sean

BobLevine

Community Expert

Do you have file extensions visible in either Finder (Mac) or File Explorer (Win)? If not, turn them on. If you do, it sounds like you have a O/S issue, not an InDesign issue.

Sean5CF1Author

Inspiring

Thank you all - great to get feedback so quickly.

So a few things.

Version control is a common feature of working and evolving files. Verson 1.0, 1.1, 1.2 then as the file evolves to predraft Version 2.0, 2.1, 2.2 then to book publishing/files publication Version 3.0, 3.1, 3.2 etc.

This is THE common file evolution standard, using another standard is not recognised good practice/governance. It works for every other software platform without problem.

As you can see the file ext. is still recognised as .indd with version control - the above files evolved with version control sometimes to 2.6 etc, without issue.

The issue seems to have begun spontaenously (after 8 years of reviewing and updating a 700 page book without issue) - but only with certain files and only with .indd.

I save a file as an .indd (in the file type section with a new version no. as per normal) and suddenly it doesn't want to recognise the file as an .indd, but rather a .1 file type.

It's bizzare and uncharacteristic of InDesign (again it only happens with InDesign).

Im trying to pin down the issue - it appears to only effect v1.1 but im trying to replicate with higher version control (1.2, 1.3. etc).

Again thank you for the feedback - I'll get back as soon as I have more info

Sean

m1b

Community Expert

The problem is that even after you find the culprit in this case, and fix it (assuming you manage to get it fixed), it may crop up at any time again in the future. The reason for this is, as I understand it, that you are relying on the programmers to not be lazy in the way they parse filename/extensions. The vast majority of frameworks (eg, built in OS frameworks talking to the filesystem) will get this right, but there will be cases where the programmer takes a shortcut and quickly matches the first dot as the delimiter, because it is more work to match the file extension correctly. So, even if you get it fixed this time, you are only fixing it this time. It will come again.

It certainly isn't correct to call the system you describe "THE common file evolution standard". I would call it "THE most common file naming mistake". I was reluctant to give it up back in the day, but the peace of mind has been well worth it, and I've lost nothing. Actually, the system I use now is superior anyway because two-alpha-characters better convey the phase of the document (as in your system 1=pre-draft, whereas mine is DR).

Anyway, some food for thought if nothing else. Hope you get it fixed and all the best.

- Mark

m1b

Community Expert

Hi @Sean5CF1, I agree with the other suggestions and I would seriously recommend never using a dot in a filename except to delineate the file extension. I used to do that years ago and it sometimes caused a problem and was difficult to troubleshoot. I switched my version code to 2 x alpha characters for the job phase, and then a simple integer for the version. So my version numbers these days look like "DR1", or "FA25" for example. Never looked back. If you must have a software version style, with major.minor version numbers, just replace the dot with a hyphen or underscore, so 1.1 becomes 1-1.

- Mark

Peter Spier

Community Expert

I think this is more likely an OS issue. using dots in filenames has never been considered a good practice.

Derek Cross

Community Expert

Why not use (say) filename1a.indd, filenmame1b.indd, filename1c etc and for new editions filename2a.indd and so on?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded