Since the TPM insists on listing files alphabetically, I thought I might be
able to do a little organization by putting the documentation files in a
separate segment from the files that actually generate code. But it won't let
me build the project, a single-segment code resource, on the grounds that
there's more than one segment—even though only one segment has any actual
code.
<<<
I thought I might be able to do a little organization by putting the
documentation files in a separate segment from the files that actually generate
code. But it won't let me build the project, a single-segment code resource,
on the grounds that there's more than one segment
>>>
Well, the segmentation mechanism was hardly intended to serve as a means of
organizing documentation, but I'll pass on your suggestion that the TPM check
to see whether there's at least one file in a "segment" with translator
assigned to it.
Kevin Irlen
Symantec Languages Support