Exporting Personal Books Unnecessary Hassle

Our institutional board meets monthly. I am responsible for keeping our institutional policies up-to-date. I do this on Logos as a "Personal Book." It makes it fast and easy to find any policy during board meetings.

Generally, we update some policy during our meeting. So, each month, prior to the board meeting, I send a complete copy of the up-dated board policies in pdf format to all board members.

Unfortunately, exporting the policies is unnecessarily difficult. Each section has to be individually selected. There is no convenient way to select all and export. I know the purpose was to protect copyrighted books. But there should be a way to make a "Personal Books" that is not copyrighted and can be conveniently changed and exported.

Find more posts tagged with

Desktop App

Comments

Graham Criddle

Presumably you have the source document in a .docx format.

Could you use that to produce the PDF formatted document?

Thinking

https://community.logos.com/discussion/comment/1098468#Comment_1098468

No, because it has all the Logos codes for indexing, etc scattered throughout. For example:

[[@Headword:MyToc]]

Graham Criddle

https://community.logos.com/discussion/comment/1098469#Comment_1098469

Understood - apologies, I should have thought of that!

If you right-click a section (in Print / Export) you have the option to select them all.

Does that help?

Thinking

https://community.logos.com/discussion/comment/1098470#Comment_1098470

I wish it did, but I don't have many subsections. Generally, each policy is its own section that is in table of contents. This makes it easy to jump to a section. But there are a lot of sections. What is needed is a way to indicate a private, non-copyrighted document that can be modified and export easily and quickly.

Thinking

https://community.logos.com/discussion/comment/1098471#Comment_1098471

I have a lot of documents I have placed in "Personal Books" I also wish there was a way to search for the book in the Personal Books panel to quickly jump to a book to edit it.

David Ames

https://community.logos.com/discussion/comment/1098469#Comment_1098469

Presumably you have the source document in a .docx format.
Could you use that to produce the PDF formatted document?

No, because it has all the Logos codes for indexing, etc scattered throughout. For example:
[[@Headword:MyToc]]

Just tell them to ignore items between [[ and ]]

OR try WARNING:: THIS MAY NOT WORK SO TEST FIRST (maybe do a line count before and after)

Open the file
Save with a different name so that the original file is not changed
Then on the copied file try

Before running the replace commends
Do Find [[ and verify that every [[ has a corresponding ]] on the same line

AND THAT YOUR FILE DOES NOT USE [[ NOR ]] FOR SOMETHING ELSE OTHER THEN LOGOS CODES ((Or the following replace will erase way too much))

Just to be safe do Find ]] to double insure that each ]] has a corresponding [[ before it on the same line (lots of work but maybe simpler the coping each section)

Replace [[ with ZZZ (assuming that ZZZ and YYY are not found in your file)
Replace ]] with YYY
Then use wildcards replace ZZZ*YYY with space
Where ‘*’ is from the special wildcard menu * that is 0 or more characters

David Ames

https://community.logos.com/discussion/comment/1098469#Comment_1098469

Presumably you have the source document in a .docx format.
Could you use that to produce the PDF formatted document?

No, because it has all the Logos codes for indexing, etc scattered throughout. For example:
[[@Headword:MyToc]]

Just tell them to ignore items between [[ and ]]

OR try WARNING:: THIS MAY NOT WORK SO TEST FIRST (maybe do a line count before and after)

Open the file
Save with a different name so that the original file is not changed
Then on the copied file try

Before running the replace commends
Do Find [[ and verify that every [[ has a corresponding ]] on the same line

AND THAT YOUR FILE DOES NOT USE [[ NOR ]] FOR SOMETHING ELSE OTHER THEN LOGOS CODES ((Or the following replace will erase way too much))

Just to be safe do Find ]] to double insure that each ]] has a corresponding [[ before it on the same line (lots of work but maybe simpler the coping each section)