You are viewing limited content. For full access, please sign in.

Question

Question

Character added to new files when "saved as" in Word

asked on December 12, 2018

Hello,

We have a client that has a user noticing a functionality change between Laserfiche 9 and 10.

The user creates a new file within Word, saves it to LF using the MS Office plug-in and while still in that Word file, attempts to PDF it for external use. The "save as" function keeps appending a "~" to the end of the file name. 

On the other hand, when the user opens the electronic file directly from the repository and uses the save as function, there is no name change or rather no "~" attached. 

Is there a reason the system modifies the name in one instance, but not in the other?

See scenarios and screenshots below.

Scenario 1:
1)    Open a blank word doc
2)    Click Save to LF (using LF plug-in in Word)
3)    Name the document (ignored templating) and click Save
4)    Ignore templating and click OK when prompted.
5)    Kept word doc open and clicked File > Save Adobe PDF and it defaults to the temporary folder and adds a “~” to the name.
 
Scenario 2: 

1) Closed the document, opened it from the repository (Open > Edit Electronic File).
2) The location was, in this case, a temporary folder. But upon clicking “Save as Adobe PDF”, it did not add the “~” to the end of the name.

1.png
2.png
3.png
4.png
5.png
1.png (83.28 KB)
2.png (132.89 KB)
3.png (9.17 KB)
4.png (17.93 KB)
5.png (47.23 KB)
0 0

Replies

replied on December 12, 2018 Show version history

Do you have the Adobe PDF plugin installed? I don't have any Adobe products installed, and I don't see this behavior.

EDIT: That's dumb of me. I just noticed it in one of your screenshots. My guess is that this is just how the Adobe plugin works. I can do a similar set of steps in Word (without Adobe), and it doesn't change the file name. It's not uncommon for apps to tweak the file name coming in and out of the temporary directory.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.