Comment 11 for bug 593955

@Victor, this is going to be reviewed during the new file format
implementation which will happen during v6 development. I do not have
time to discuss this issue further until after v5 is release. When I
open the discussion on the new schematic file formats, feel free to comment.

On 1/8/2018 3:02 PM, Victor wrote:
> Wayne, maybe solution of this problem would be to create a new file
> format - just slighly changed, with new parameter stored (measurement
> units) in every file? Users who use existing libraries - use "old
> format" without measurement units determined. Users can store their
> files in both formats, old (without) and new (with determined
> measurement units), but new format is preferable. There will be two
> formats in use.
>
> There is a sample file with circuit with three wires, without component
>
> * * *
>
> EESchema Schematic File Version 4
> LIBS:test-cache
> EELAYER 26 0
> EELAYER END
> $Descr A4 11693 8268
> encoding utf-8
> Sheet 1 1
> Title ""
> Date ""
> Rev ""
> Comp ""
> Comment1 ""
> Comment2 ""
> Comment3 ""
> Comment4 ""
> $EndDescr
> Wire Wire Line
> 3650 3650 3650 3050
> Wire Wire Line
> 3650 3050 5300 3050
> Wire Wire Line
> 4850 3750 5700 3750
> Wire Wire Line
> 5700 3750 5700 3300
> Connection ~ 5700 3750
> Wire Wire Line
> 5700 3750 5950 3750
> $EndSCHEMATC
>
> * * *
>
> Changes of file format:
>
> EESchema Schematic File Version 5 (next step)
> EEUNITS [mil/mm] (new parameter)
>
> That's all in file format!
> Program must determine string "EEUNITS" in file and multiplicate all dimensions of schematic.
>