Notes from 3/20/2020. For 2021 Calendar.
These notes are from memory. Take with a grain of salt.
Prerequisites:
Have verses selected for gospel and believers versions. Preferably all verses are ready & final proofed. But if not, start with the verses you have ready.
General Order of Operations
Copy & paste last year's verse set xml to this year's project folder. & rename
Put exported JNC verses into the current year's project folder.
May need to bug Dan for files. (Or they're exportable from Falcon.Bridge. I'm not sure)
Coming from dan, there are MOST likely file naming problems.
Go through each language & fix.
You’ll probably see verses that don’t have the English references in the name (they still have the ref in their language)
Only 1 underline between 2 references in 1 file.
Often, if it’s messed up in 1 language, it will be messed in most / all.
If xml reader can’t find it, you’ll probably need to change it. If it still doesn’t recognize it, it can be manually assigned to the month in the xml reader.
Once the new verses have been created, the .png's need to be created.
Open a verse file, and export it as .png with Max Quality, 72dpi, grayscale & transparent background. This saves the indesign settings for the next step.
Now run the 'batch_convert.jsxbin' (or no .jsxbin) from indesign. (screenshot below)
Select the input folder for each language for the new year.
The output folder should match the input folder.
Select PNG
Drag and drop all the newly created png’s to pngGauntlet. (this helps GPC web page load time) and click optimize.
Once optimized, copy the indd’s & png’s to the corresponding language in the verse repository: X:\Print & Ebook Projects\Calendars\GPC\Verse Resources. Please make sure to overwrite old files. (the only exception to this may be artistic versions.)
Open newly copied set in xml reader.
Create new sets for each languages that you have verses for.
(some languages only have a 4 page calendar in JNC)
Each new set needs:
A new set ID. (Try to continue number pattern with similar language / GospelBelievers category)
To be marked as featured
Previous year's featured set needs to be renamed & unmarked as featured.
This is a feature I wish was built into xml reader, but isn't yet.
Once the sets are created, Update the new English Believers & Gospel verse sets with the new references & file names.
There is a 'Default' set that can be used to update the references of the other new sets with the verses used.
Right click & click ‘Update Default References’
Update this default set for both believers & gospel versions.
Go through each new set and update from the default set.
Right click on the xml reader (near monthly verses) and click ‘Update This Set’ for EACH new language set.
This will update the references to match the default reference.
It will also try and find a matching verse .indd file.
Manually match any missing files.
Rename if necessary.
If renaming, make sure to rename the originals too.
They can be manually assigned by right clicking on the verses as shown here:
The next step is to go through and put the verse text in for each month.
Open each new set, and for each month, click the ‘open’ button. This will open Indesign. Copy the verse text and paste it in the verse text box.
Make sure that all text is pasted. I tried to implement a fix, but sometimes when there’s a (soft/hard?) return in InDesign, it won’t put the complete text in, just the first line.
Be sure to save periodically!
The ‘Keep Changes’ button updates the database in memory. It keeps any changes made when you switch from set to set, but it doesn’t save to xml.
I like to then update any verses that have a matching indesign file.
Open each new set and,
Right click and click ‘Update all matching text fields’
This will update any verse that has been matched to a new file. (Read the tooltip for more info.)
After the new sets have been created, go through each set, (all of them including the old ones) and make sure that the filename textbox is green and there is an image for each month.
This means that an .indd file & a .png file were found.
I ‘think’ that the next step is to export the data.
Click the ‘Export Data’ button. (Basically this process copies files from 2021 Production and the newly generated 2022 Print and Ebooks into a 2022 Production folder. Some xml files (Creation facts, Daily verses, need to be moved to language specific 2022 Production folders manually. Overall Verse Sets, Monthly Grids and Holiday sets move to the root 2022 Production folders.) All of this inside of X:\Production\Resources\Personalize\GospelOfPeace)
Click the ‘Open Verse Sets XML’ button.
Select & open the xml set for the year prior to the one you want to export.
It will populate the files it needs to copy for the next year.
Double check a few (all?) of the items to make sure it generally looks ok.
Make sure that the current year & export year are correct. (IMPORTANT!)
Click the ‘Export’ button. It will take a few minutes to copy everything over.
This doesn’t migrate / create:
The Next Year Calendar pdf & png.
The verse set xml?
The daily verses?
I forget what all ... Check & compare against the previous year to see what’s missing.
The next step is to update Falcon.Bridge. Open this folder: X:\Computer\Falcon Software\Bridge
I think there’s 2 main files to update:
Bridge-Configuration.xml
Under GospelOfPeaceCalendar > RootFolder > Update folder path
Bridge-Configuration-GPC.xml
Update the year and the 14 file paths at the beginning of the file.
At the end of the file, update the set id’s to match the newly created set id’s
Check the other xml’s in the above folder to see if there’s any other pertinent info.
Open bridge and run: ‘Version pageup (IDML)”
In the selection options, make sure everything’s selected except nepali & Danish ... I think
It will create idml versions and put them in the final folder.
Now it’s necessary to create the next year calendar for each language.
Use the 'batch_convert.jsxbin’ to convert each idml to indd. (This helps with file renaming. If opening an idml, indesign doesn’t keep the name. Instead it names it untitled-1 ... or something like that)
I put the new .indd files in a temp sub folder
Open each, and export a pdf of page 26. (the next year calendar)
Keep naming consistent.
The final name should be “Next Year Calendar-Language.pdf”
Crop pdf. I created an acrobat action. These are the crop measurements:
Crop:
Top: 0.65”
Bottom: 2.4”
Left: 0.55”
Right: 2.43”
Create a new indesign doc, place the pdf, and export as png with the same name as the pdf. (The reason to do this in InDesign rather than direct in Acrobat is that the InDesign export seems to give a better quality PNG output. The Custom INDD should be exactly the dimensions of the cropped PDF: W:8.020in H:5.450in).
Move each to the correct folder: resources folder\YEAR\Language\Design\Next Year Calendar-Language.pdf/.png
Generate a master Monthly Grid by taking one of the INDD Calendar files just generated and delete all the information EXCEPT the gridlines. Save as YYYY Monthly Grids.indd and place in resources folder\YEAR (compare to the prior years files to check yourself)
Sigh, you should be finally ready to create the final .indd files for the different sets.
These will be placed in the Print & eBooks section with the idml and indd files you generated in the prior step.
In Bridge, run ‘Version Pageup’ under the Gospel of Peace Calendar menu.
It will check your memory with this:
Check the calendars you want exported, click OK, and wait a while.
Work by analogy from the prior years structure. As of this writing the prior years production folder is here: X:\Production\Resources\Personalize\GospelOfPeace\Composed\2021 Stock Versions
In general, all files (whether stock or truly custom) will fall somewhere inside X:\Production\Resources\Personalize\GospelOfPeace\Composed
Files that were marked as -Final by Falcon Bridge in the prior step now need to be manually moved to this years \YYYY Stock Versions folder
AND be relabeled so that the Item# comes first in the file name.
AND have the Graphics Layer turned off.
AND have a production PDF generated from that INDD. (Output using the {High Quality Print(1200)} preset. This may do everything as an image so that it eliminates potential font substitutions.)
AND have a proof print done on the collated body stock for the GP of that year. This would be the time to mark the drawers of the printers for the year with the “taped down graphic” that shows the proper orientation of the years collation body sheets and cover sheet.
After someone proofs the final calendars, these two options can be run in bridge:
They will create the images for the custom site, and the images for the product site.
Run Web sync to upload the product images
Once you think you have everything assembled, create a 7zip of the resources folder. This reduces the size from 1+gb to about 100mb. Upload the whole folder to .com/.net/.info (whichever one is the chosen test site.)It will need to be unzipped to the corresponding folder.
I don’t think that .indd files need to go up, but it’s just easier to upload the whole thing.
Test the site, and do fixings as needed.
Congrats!
[4/9/21 4:50 PM] Chris Buchanan for 2022 GP Calendars
English—Believers Artistic
Spanish—Believers Artistic