This is shot in the dark, but are you using exclusive locks and the
svn:needs-lock property? If so you might need to get locks for more than
just the file you're opening.


-----Original Message-----
From: framers-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of
mbradley at techpubs.com
Sent: Tuesday, April 08, 2008 2:40 PM
To: framers at lists.frameusers.com
Subject: Text Inset Problem with TortoiseSVN

My client started using imported text insets for some boilerplate
paragraphs. In the folder tree, the folder of boilerplate source files
is at the same level as the folder of the FM book. Both folders are
checked into TortoiseSVN, an open-source client for Subversion, a
version-control program.

Every time a different writer opens a FM file that uses one of the text
insets, s/he gets an error message from FM saying the text inset is
unresolved. Re-importing the text inset fixes the problem for that
writer. Every writer opens the same FM file and imports the same text
inset, so there's no reason for FM to lose the link. We copied both
folders to a location outside SVN and the problem did not occur, so it
has something to do with SVN. 

By the way, the book folder contains a subfolder of Xrefed image files,
and SVN doesn't interfere with those links. We're going to try Xrefing
the text insets instead of importing them, but Xrefing them means we
lose the formatting and markers (Index and Hypertext) in the source

So ... anyone know what's going on here with SVN?

= Mike Bradley


You are currently subscribed to Framers as
mike.feimster at acstechnologies.com.

Send list messages to framers at lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscribe at lists.frameusers.com
or visit

Send administrative questions to listadmin at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Reply via email to