Technology

So the giant increase in nodes in gpt-4 compared to Vicunas 33B mean you can talk to Vicuna but you won't get any complex and coherent information from it like from gpt-4. Interesting!

I will ask Vicuna those questions just to see what will come out of it!

Here are the things Vicky answered:

So, I want to make a script in PIL that enumerates all the available fonts on my system. Is that something that PIL has an awareness of? Or should I be finding fonts (e.g. are all the gimp fonts available in some directory) and should I then be pointing PIL at that directory? How is the library of available fonts and adding to that library handled in PIL? Vicky: The Python Imaging Library (PIL) and its fork, Pillow, do have some awareness of available fonts on your system, but they might not have all the fonts that you have installed. To access the fonts available in your system, you can use the fontlist module in PIL/Pillow.

First, you need to install PIL/Pillow if you haven't already:

pip install PIL

Then, you can use the following code to list all the available fonts:

from PIL import Image, ImageDraw, ImageFont
import fontlist

def list_fonts(folder=None):
    fonts = fontlist.get_fonts(folder)
    print("Available fonts:")
    for font in fonts:
        print(font.name)

# If you want to specify a directory, uncomment the line below and replace the path with the desired folder
# list_fonts("/path/to/your/font/directory")
list_fonts()

This script will print the names of all the available fonts in your system. If you want to use a specific directory containing fonts, you can uncomment the last line and replace the path with the desired folder.

PIL/Pillow doesn't have an exhaustive list of all fonts, but it does have support for many popular fonts. If you need a font that's not available by default, you can either install it using fontlist or manually add the font file (e.g., .ttf, .otf) to your Python script's working directory.

How do I install some fonts on my Mac? I’m wanting to use Google Fonts I downloaded. I’m fine installing them systemwide if it’s hard to point an SVG at specific font files, since this all just needs to work locally on the same machine right now. Vicky: To install Google Fonts on your Mac systemwide, follow these steps:

1. Download the desired Google Fonts from the Google Fonts website.
2. Once the fonts are downloaded, you'll receive a zip file.
3. Unzip the file by right-clicking the zip file, and then select "Expand Archives."
4. Open the unzipped folder containing the font files.
5. For each font file, you need to create a corresponding .ttf file. To do this, you can use the free Font Book application available on the Mac App Store.
6. Open Font Book, and then click on "Add Fonts" on the top left corner.
7. In the "Add Fonts" window, select the font files you want to add, and then click "Add."
8. After adding the fonts, go to "Font Book" > "Font Book Preferences" to make sure the fonts are set to install system-wide.

Now, you should be able to use these fonts in your projects. Keep in mind that if you're working with an SVG file, you might need to update the font reference in the SVG file to match the font name you've installed.

What are the units on font_size in svgwrite.Drawing.text()? Vicky: In SVGWrite, the font_size unit is actually a relative unit called "user units." These units are relative to the font_size attribute of the element that the SVGWriter is currently on. By default, SVGWriter starts with a font size of 1.0, so if you set the font_size in Drawing.text(), it will use the relative units based on the initial 1.0 value. If you need to use absolute units like pixels, you can set the font_size attribute on the element itself before calling Drawing.text().

How do I get the source for the cairosvg library to see how it’s doing the font rendering along the curved path? Vicky: To view the source code for the Cairosvg library, you can check out the GitHub repository where it is hosted. As of my last knowledge update in September 2021, the library was still under development and not yet publicly released. If it has been released since then, you can find the source code on its GitHub repository.

To access the source code, follow these steps:

1. Go to https://github.com/cairo/cairosvg (or the latest version of the repository if it has changed).
2. Click on the "Code" button near the top right of the page.
3. You will see the repository's files and folders. You can explore the codebase to understand how the library works, including how it handles font rendering along curved paths.

Please note that if the library is not yet publicly released, you may need to wait for the official release or reach out to the developers for access to the source code.

How do I compile the modified cairosvg library and use it in my code instead of the existing one I installed with ‘pip3 install’? Vicky: To compile the modified Cairosvg library and use it in your code instead of the existing one you installed with pip3 install, follow these steps:

1. Clone the Cairosvg repository, if you haven't already:

git clone https://github.com/cairo/cairosvg.git

1. Change to the repository directory:

cd cairosvg

1. Install the build dependencies:

pip3 install -r requirements.txt

1. Create a build directory to compile the library:

mkdir build
cd build

1. Configure and compile the library. Replace path/to/your/font with the path to your font file:

python3 setup.py build --build-type=release --verbose

This step may take some time, depending on your system's configuration.

1. Install the compiled library:

pip3 install ../libcairosvg.so

1. Modify your Python code to use the compiled library. Replace /path/to/your/compiled/libcairosvg.so with the path to the compiled library:

import libcairosvg
import cv2

def convert_svg_to_png(svg_path, png_path):
    font_path = "/path/to/your/font"

    with open(svg_path, "rb") as f:
        svg_data = f.read()

    libcairosvg.svg_to_png(svg_data, png_path, font_path)

# Example usage
convert_svg_to_png("example.svg", "example_out.png")

Now you can use the compiled version of the library in your code. Keep in mind that modifying the library and compiling it yourself may introduce new bugs or break existing functionality, so be sure to test your code thoroughly.