How to load data from Google Webfonts to TiDB

Start by listing all the fonts you need from Google Web Fonts. Visit the [Google Fonts website](https://fonts.google.com/) and note down the required font names, styles, and any specific metadata (like font weight, category, etc.) that you need to transfer to TiDB.

For each font identified, download the font files directly from Google Web Fonts. You can do this by selecting the font on the Google Fonts website, clicking the "Download family" button, which typically downloads a ZIP file containing all the font styles (e.g., regular, bold, italic) in TTF or OTF format.

Once downloaded, extract the ZIP files and organize them into a structured directory on your local machine. Create a directory for each font family, and within each, store the respective font styles as separate files. This organization will help in the subsequent steps of uploading to TiDB.

Ensure you have a TiDB cluster set up and running. You"ll need to have access credentials ready. If not set up yet, follow the [official TiDB documentation](https://docs.pingcap.com/tidb/stable) to deploy a TiDB cluster locally or on the cloud.

Connect to your TiDB instance using a MySQL client, as TiDB is MySQL-compatible. Create a database and necessary tables to store font metadata and binary data. For instance:
```sql
CREATE DATABASE google_fonts;
USE google_fonts;

CREATE TABLE fonts (
id INT AUTO_INCREMENT PRIMARY KEY,
name VARCHAR(255) NOT NULL,
style VARCHAR(255),
weight INT,
category VARCHAR(255),
file_path VARCHAR(255)
);
```

Using SQL `LOAD DATA INFILE` or `INSERT INTO` statements, populate the `fonts` table with metadata and file paths pointing to where the font files are stored on your server. You need to upload the files to your server and reference their paths in the table:
```sql
INSERT INTO fonts (name, style, weight, category, file_path)
VALUES ('Roboto', 'Regular', 400, 'Sans-serif', '/path/to/roboto-regular.ttf');
```

Finally, verify that the data has been successfully transferred by querying the TiDB database and checking the entries in the `fonts` table. Ensure that all necessary metadata and paths are correctly stored. You might want to perform a sample check by downloading a font using the stored file path to ensure it"s accessible.

This process allows you to manually move the font data from Google Web Fonts to TiDB without using external connectors, while maintaining control over the data organization and storage.