Image 1 — One part, both formats, measured after import (placeholder). Export a 100 mm square with a 20 mm hole placed off-center, so an orientation or mirroring error is visible, then import the SVG and the DXF into the same application and capture them side by side. Show the measured geometry and both overall dimensions and state the application and version, the export settings and the import unit and DPI choices used. Capture the imports as they arrive; do not repair them first. Produce this as a reproducible software capture with a downloadable sample file, not a photograph of a screen.
Image 2 — Color to layer, then layer to operation (placeholder). Show the layer list immediately after import and operation assignment as a clearly separate second step, so the two are not confused. Disclose the exact RGB values used, how black behaved, the application version and any layer configuration already stored in the destination project. Label the rows in text rather than relying on color alone and omit numerical machine settings.
Image 3 — What you see is not the path the machine follows (placeholder). Show one thick stroked line in three panels: normal view, path or outline view and after an intentional outline expansion. Label the path the software would follow in each case, so the single center path and the two boundary paths are unmistakable. Add node markers rather than relying on color alone and state the application and version.Image 4 — A hole that looks correct and imports wrong (placeholder). Use a controlled compound-path or clipping example in four panels: source appearance, the actual paths underneath, the destination preview showing the failure and the corrected geometry. Name the exact unsupported feature or export choice that caused it, state both applications and their versions and supply the sample file so the failure can be reproduced.
Image 5 — Curve representation and tolerance (placeholder). Compare a known circular arc with a coarse straight-segment approximation and a sufficiently fine one and state the measured deviation for each. Identify the exported entity types: an LWPOLYLINE carrying bulge values is the valid arc example. Read the entity types from the exported file or an entity-property inspection, because a destination application may normalize entities internally and its node display alone cannot prove what the file contained. For the duplicate-path case, show a selection count or a labeled displaced overlay: identical overlapping lines are invisible in a screenshot.
评论
正在加载评论...