[277412] in TECHWR-L
Re: [TECHWR-L] - What are your experiences with version control
daemon@ATHENA.MIT.EDU (Tony Chung)
Wed Dec 10 18:14:47 2025
MIME-Version: 1.0
In-Reply-To: <731fdd1e-9af5-45e0-b5f6-f0b78b590df5n@techwr-l.com>
From: Tony Chung <tonyc@tonychung.ca>
Date: Wed, 10 Dec 2025 15:14:13 -0800
Message-ID: <CAPnOPiH1sY3ic2GA3Y7gxXggGViT8c74YG=Hi=H8RLgg9dVKgA@mail.gmail.com>
To: techwr-l@techwr-l.com
Content-Type: multipart/alternative; boundary="00000000000066e01d0645a13013"
Reply-To: techwr-l@techwr-l.com
--00000000000066e01d0645a13013
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hey Nina. I=E2=80=99m firmly entrenched in the docs-as-code world now but w=
e used
to use DITA and the worst part about any VCS was that it did not understand
XML to manage differences at the object level rather than as characters in
source code. A quick AI assisted Google search mentioned editors like
Oxygen and XMLSpy act as an XML-interpreter for their Git integration. So
while Git sees the diffs in the code, the editor=E2=80=99s integration reco=
gnizes
the differences in the objects.
That might be the way to go, short of a full on CCMS with database and
version control.
Regarding merge conflicts, the only solution for that is to merge commits
to different files. You don=E2=80=99t need an automated locking system. Jus=
t a way
to communicate that writer A is working on this block of files and writer 1
on another set.
Just my two cents.
-Tony
--=20
TechWR-L is the =E2=80=9CTechnical Writers List=E2=80=9D =E2=80=94 an email=
discussion list focused on all issues in technical communicatio
---=20
You received this message because you are subscribed to the Google Groups "=
TECHWR-L Email Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to techwr-l+unsubscribe@techwr-l.com.
To view this discussion visit https://groups.google.com/a/techwr-l.com/d/ms=
gid/techwr-l/CAPnOPiH1sY3ic2GA3Y7gxXggGViT8c74YG%3DHi%3DH8RLgg9dVKgA%40mail=
.gmail.com.
--00000000000066e01d0645a13013
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Hey Nina. I=E2=80=99m firmly entrenched in the docs-as-co=
de world now but we used to use DITA and the worst part about any VCS was t=
hat it did not understand XML to manage differences at the object level rat=
her than as characters in source code. A quick AI assisted Google search =
=C2=A0mentioned editors like Oxygen and XMLSpy act as an XML-interpreter fo=
r their Git integration. So while Git sees the diffs in the code, the edito=
r=E2=80=99s integration recognizes the differences in the objects.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">That might be the way to go, sho=
rt of a full on CCMS with database and version control.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Regarding merge conflicts, the only solutio=
n for that is to merge commits to different files. You don=E2=80=99t need a=
n automated locking system. Just a way to communicate that writer A is work=
ing on this block of files and writer 1 on another set.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Just my two cents.</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">-Tony=C2=A0</div>
<p></p>
-- <br />
TechWR-L is the =E2=80=9CTechnical Writers List=E2=80=9D =E2=80=94 an email=
discussion list focused on all issues in technical communicatio<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;TECHWR-L Email Discussion group" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:techwr-l+unsubscribe@techwr-l.com">techwr-l+unsub=
scribe@techwr-l.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/a/techwr=
-l.com/d/msgid/techwr-l/CAPnOPiH1sY3ic2GA3Y7gxXggGViT8c74YG%3DHi%3DH8RLgg9d=
VKgA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://group=
s.google.com/a/techwr-l.com/d/msgid/techwr-l/CAPnOPiH1sY3ic2GA3Y7gxXggGViT8=
c74YG%3DHi%3DH8RLgg9dVKgA%40mail.gmail.com</a>.<br />
--00000000000066e01d0645a13013--
