How to Use AutoCAD LIN Files in BricsCAD, DraftSight, and ZWCAD
BricsCAD, DraftSight, and ZWCAD support AutoCAD-like linetype workflows and can read many LIN definitions. Compatibility is strongest for simple dash-gap patterns. Text styles, SHX shapes, paths, commands, and plot output require application-by-application testing.
A portable library separates standard LIN syntax from product-specific installation details.
Understanding LIN File Compatibility
Do not judge compatibility only by whether the file loads. A production test must verify pattern proportions, text font, symbol shape, orientation, curves, blocks, layouts, and PDF output in each target application and version.
Simple vs. Complex Linetype Compatibility
Dash-Gap Patterns
Definitions using positive, negative, and zero numeric elements are the most portable. Keep formatting conservative and avoid redefining application-supplied names.
Text-Based Patterns
The target drawing must contain a compatible text style pointing to an available font. Text width and baseline can vary when substitution occurs.
SHX Shape-Based Patterns
The correct compiled SHX file and shape name must be available. Shape compilation or search paths can differ, so ship both source documentation and the tested compiled resource.
Use LIN Files in BricsCAD
Locate the Linetype Manager
Open the application’s linetype interface or use the command-line linetype command. Confirm the selected drawing and current profile.
Load a Custom LIN File
Browse to the controlled file, select the required definitions, and create long test geometry. Do not assume an existing same-named definition was replaced.
Configure Support Paths
Add the company folder through BricsCAD settings for repeat use. Verify the path on every workstation and avoid personal profile locations.
Use LIN Files in DraftSight
Load a Custom Definition
Use the LineStyle or linetype management workflow for the installed edition and load the definition from the custom LIN file.
Assign It to Layers and Entities
Prefer layer assignments and verify that imported DWGs preserve the intended names and properties.
Resolve Missing Dependencies
Install or map required fonts and shape resources. If a shape-based pattern fails, test a simple definition from the same file to separate syntax from SHX dependency.
Use LIN Files in ZWCAD
Load a Custom Definition
Load the LIN file through the linetype manager or command workflow and assign the pattern to a controlled layer.
Add LIN and SHX Search Paths
Configure a stable support location for both the source library and compiled shapes. Reopen the application to confirm persistence where necessary.
Test Complex Linetypes
Test text rotation, shapes, curves, short segments, and plotting. Record any version-specific limitation in the company compatibility matrix.
Standard Imperial and Metric LIN Libraries
Each product may ship standard libraries with familiar names, but numeric definitions and search locations can vary. Use your controlled custom files and the unit policy from metric versus imperial linetype scaling rather than relying on a filename alone.
Text Style and Font Compatibility
SHX Fonts
Confirm the file exists, the target application supports it, and the drawing text style points to the intended resource.
TrueType Fonts
The font must be installed according to the operating system and licensing rules. Substitution can change character width and PDF size.
Missing Style Names
A LIN descriptor references a style name, not only a font file. Create the approved non-annotative style in the drawing or template before loading the linetype.
SHX Shape Compatibility
File Locations
Place the SHX in a support folder recognized by the target product. A location valid in AutoCAD is not automatically configured elsewhere.
Shape Names
The descriptor’s shape name must exist in the compiled file. A same-named SHX from another vendor may contain different definitions.
Compilation Differences
Compile and validate the shape using the documented workflow for the production environment. Retain the source SHP so a compatible build can be produced if required.
Common Cross-Platform Differences
Pattern Scale
Drawing units, defaults, and layout display settings can make the same code appear different. Use one test DWG and recorded system variables.
Text Orientation
Compare R and U behavior on reversed and curved geometry using the orientation test procedure.
Curved Geometry
Circles, splines, and tight radii reveal differences that are not visible on straight samples.
Plot Output
Use each application’s standard PDF driver and compare lineweight, font handling, symbol output, and file size.
Build a Portable LIN Library
Use Relative Folder Structures
Package LIN, SHX, fonts where distribution is permitted, test drawings, and readme files in one predictable structure.
Avoid Product-Specific Paths
Do not store absolute user or installation paths in deployment instructions. Configure a company root per application.
Include Every Dependency
List text style names, font filenames, shape filenames, units, tested versions, and expected plot settings.
Cross-Platform Linetype Test Matrix
| Test | AutoCAD | BricsCAD | DraftSight | ZWCAD |
|---|---|---|---|---|
| Simple LIN loads | Record | Record | Record | Record |
| Text style/font | Record | Record | Record | Record |
| SHX shape | Record | Record | Record | Record |
| Reversed and curved | Record | Record | Record | Record |
| Model/layout scale | Record | Record | Record | Record |
| PDF output | Record | Record | Record | Record |
Recommended File-Sharing Checklist
- Use unique custom names.
- Include the source LIN and required SHX files.
- Document text style and fonts.
- State metric or imperial assumptions.
- Provide a test DWG with straight, curved, and reversed samples.
- Provide an approved reference PDF.
- Test on the exact target product versions.
- Use the dependency packaging checklist for delivery.