Re: New name for terraSync index files

"Frederic T." <[email protected]> Mon, 13 Jul 2026 17:13:38 +0200
Newsgroups gmane.games.flightgear.devel
Message-ID <CABg8F9SCCx8VkWe6P4sM=SeKZn24DvoHe=gkxXkjWYWrHs_bJg@mail.gmail.com>
--===============0033880724188031990==
Content-Type: multipart/alternative; boundary="00000000000099637a06567f897f"

--00000000000099637a06567f897f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

dirIndex.terrasync is the most logical IMO (although, make it all lowercase
perhaps ...) because:
* it is a directory index file
* designed to be written and read by terrasync, not a text editor (so no
.txt extension)

Am Mo., 13. Juli 2026 um 17:02 Uhr schrieb James Turner <
[email protected]>:

> Hello,
>
> As mentioned in another thread, I need to rename the index files used by
> TerraSync. Currently they are called =E2=80=98.dirIndex=E2=80=99 which ma=
kes them hidden on
> Unix systems, but the Bunny Storage layer doesn=E2=80=99t like that.
>
> There=E2=80=99s a few sensible-seeming options for what to rename them to
> (actually duplicate, rather than rename, for $reasons, on the server side=
).
> Fortunately the files are tiny, duplicating them is no big deal.
>
> Possibilites:
>
>         dirIndex.terrasync
>         terrasync.dirIndex
>         dirIndex.txt
>         terrasync-dirIndex.txt
>
> The files are text, but not meant for manual editing, so I=E2=80=99m unsu=
re if a
> .txt extension is a good idea or will encourage end-users to think they c=
an
> edit the files, when they in fact, cannot.
>
> If anyone has a reason why one of the above is preferable to the others,
> please let me know.
>
> Note that we can=E2=80=99t use special characters in the filenames, but t=
his means
> the location in a lexicographically sorted list will not be consistent - =
we
> have files with =E2=80=98all kinds of names=E2=80=99, and I don=E2=80=99t=
 want to call the files
> something like AAA_dirindex.
>
> This will be back-ported to 2024.1.7: support for the old names on disk
> will be kept of course, so that an existing TerraSync download continues =
to
> work.
>
> Kind regards,
> James
>
>
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>

--00000000000099637a06567f897f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">dirIndex.terrasync is the most logical IMO (although, make=
 it all lowercase perhaps ...) because:<br>* it is a directory index file<d=
iv>* designed to be written and read by terrasync, not a text editor (so no=
 .txt extension)</div></div><br><div class=3D"gmail_quote gmail_quote_conta=
iner"><div dir=3D"ltr" class=3D"gmail_attr">Am Mo., 13. Juli 2026 um 17:02=
=C2=A0Uhr schrieb James Turner &lt;<a href=3D"mailto:[email protected]">=
[email protected]</a>&gt;:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">Hello,<br>
<br>
As mentioned in another thread, I need to rename the index files used by Te=
rraSync. Currently they are called =E2=80=98.dirIndex=E2=80=99 which makes =
them hidden on Unix systems, but the Bunny Storage layer doesn=E2=80=99t li=
ke that.<br>
<br>
There=E2=80=99s a few sensible-seeming options for what to rename them to (=
actually duplicate, rather than rename, for $reasons, on the server side). =
Fortunately the files are tiny, duplicating them is no big deal.<br>
<br>
Possibilites:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dirIndex.terrasync<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 terrasync.dirIndex<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dirIndex.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 terrasync-dirIndex.txt<br>
<br>
The files are text, but not meant for manual editing, so I=E2=80=99m unsure=
 if a .txt extension is a good idea or will encourage end-users to think th=
ey can edit the files, when they in fact, cannot.<br>
<br>
If anyone has a reason why one of the above is preferable to the others, pl=
ease let me know. <br>
<br>
Note that we can=E2=80=99t use special characters in the filenames, but thi=
s means the location in a lexicographically sorted list will not be consist=
ent - we have files with =E2=80=98all kinds of names=E2=80=99, and I don=E2=
=80=99t want to call the files something like AAA_dirindex.<br>
<br>
This will be back-ported to 2024.1.7: support for the old names on disk wil=
l be kept of course, so that an existing TerraSync download continues to wo=
rk.<br>
<br>
Kind regards,<br>
James<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Flightgear-devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank"=
>[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/flightgear-devel" r=
el=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/lis=
tinfo/flightgear-devel</a><br>
</blockquote></div>

--00000000000099637a06567f897f--


--===============0033880724188031990==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============0033880724188031990==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--===============0033880724188031990==--