I’m not sure if it matters what order it is in, but it works this way. Create a second layer, rename it “tabs.” Move it below the first layer as a matter of convention.Move the letters together so they overlap, convert object to path, cut path, then ungroup and then union it so it removes the extra lines. This only matters because it helps you see the cuts that will overlap and where to put in tabs later. If text, change fill to none, set stroke paint to black and stroke style to 3 mm or 4 mm (3.175 mm if you want to be precise) for 1/8" bit or 6 mm or 7 mm (6.35 mm) for 1/4" bit. There is extra difficulty coming from the fact that I am using images, iframes and other unusual elements inside the HTML, which means I cannot use SVG as a solution which would have been easy.After some editing, I have my shape as an outline only with the thickness of the line the same size as my cutting bit so I can see what it will look like. So, now I want the text to be separated into pages automatically just like when you write in a text editor like Word, only you're writing HTML code. Otherwise, each time I wanted to change something in one page and the text didn't fit anymore, I had to re-edit all the pages manually again, pushing all content down or up, in each page, which is mad. I remembered that I want to be able to edit the content of the white paper directly from the HTML and allow a JS function to separate the content dynamically. My original intention was to create a fully responsive A4 ratio container for each page and write text manually in each page element (this was a nice challenge on it's own and I succeeded to make the container the perfect ratio on any screen, but trying to make the text look the same on any screen seemed impossible), so I gave up. Research has proven that this challenge has yet to be taken down clearly by anyone on the internet.
Working on a responsive white paper for an open-source project.
0 kommentar(er)
