IPC144 VS SVGcode

Reviewing two PRs from a classmate is one of the duties for this project. The PRs, as well as my reviews, are available here and here. Both of the PRs I reviewed were really well-written and detailed, with very few mistakes. It was interesting to observe how different people approached certain changes, such as adding a svg file.

For this assignment we had to contribute to a Seneca repository. I chose the IPC144 repo.

Issue: https://github.com/Seneca-ICTOER/IPC144/issues/64 I worked on the standardized front matter across all markdown pages. This open-source project is the C language course notes of my major program.

And the reason why the web-only artifacts is still appear on the PDF page is because the --excludeSelectors option is not implemented enough. I have to add .clean-btn to the --excludeSelectors, the purpose of this is not to include the "On the page" artifact in side the PDF page. This is the final source code I have implement for this improvement and my pull request

I think I was able to do a good job meeting my goals I gave myself in my planning phase of this release. I was able to finish the issues well on schedule while balancing my other courses like I hoped and I was able to properly audit and fix both issues #122 and #123 without needing too many changes after review. What I learned from those two issues is the importance to read and checkout other issues/pull requests, especially for smaller repos. As I was told in the review for both my issues, I learned that the project recently made changes with how we would format the frontmatter. In PR #142 we no longer use the slug for pages due to inconsistency with links and we also need to include a description to follow the standardized Frontmatter as updated in PR #143.

The first issue I was working on IPC144 Course Note is about improving the usability of the PDF file generated from the website. All contents are generated inside the PDF, however, we want to get this better since some of the pictures are not showing properly, and also the web-only artifacts are still on the PDF, which we do not want it when we use the "PDF" version. convert-to-pdf.sh file would be modified a bit to accomplish this.

Issue #113

PR

As for this pull request, the code review went much more smoothly, with me having to only make minor changes to ensure that it would not cause any errors when built.

2. #issue-107

Raster Image to SVG Converter

here are some options -- potrace is free, or https://svgco.de/... there's also this extension that puts them in an a1111 extension. Illustrator also has a function for it, if you have access

Thanks to SVGCode (https://github.com/tomayac/SVGcode) which did already my idea to compile POTRACE into WebASM/JS so to get rid of exectuables and faster inbrowser-vectorizing (the guy in the input example image is Richard Feynman)

Oh op use this for png to svg conversion if you do not have better Ai or pro design tools. https://svgco.de

This issue was about experimenting with SVGCode to see if it could be used to convert raster images to SVGs. I blogged about this process in my last post. I created a pull request which demoed the results of my research by including several SVGs that I created using SVGCode, Adobe Illustrator and Inkscape. Overall, I think that Inkscape produced the most consistent results for coloured and black and white images compared to other tools I tried, which I mentioned in my PR.

In a previous post, I mentioned working on an issue for converting raster images to SVGs. This week, I did some research on the tool recommended in the issue, SVGCode, as well as other popular tools and in this post I will be discussing some of what I learned after trying them out. For the tools that I tried, I wanted to find something that is free and easy to use, while still creating high quality SVGs, as there are a lot of images to convert. (Disclaimer: I'm pretty new to working with images and image editing software so I'm probably not using all the right terminology here, but I'm trying to learn!)

Thanks for the kind words! The documentation is still missing (tracked in part as https://github.com/tomayac/SVGcode/issues/19), but Potrace, the library SVGcode is based upon, has detailed information in a PDF on all parameters: http://potrace.sourceforge.net/potracelib.pdf.