I'm working on migrating source into RTC and continue to struggle with
handling of line delimiters.

The online help says:

By default, when you share a project or check in a newly-created file,
Jazz source control examines the content and sets the file's line
delimiter property to the value Platform. (If the file appears to be a
binary file or has an inconsistent set of line delimiters, its line
delimiter property is set to none (binary).) When you load a file with
Platform line delimiter property into a local workspace, Jazz source
control determines the file's MIME content type and sets the line
delimiter to match the platform convention for that content type.

I'm not seeing this behavior. I tested creating a couple of text files,
one with no extension and one with an extension which is not defined in
the File Properties preferences. Based on the description above, I would
expect these to be "tagged" as "Platform" and line delimiters set
appropriately when the files are loaded on a given platform. Rather,
they are tagged as "Binary". Is this a bug, or is the documentation
incorrect?

I was working around this issue by scanning source files and attempting
to differentiate binary versus platform prior to sharing, and setting
File properties to cover all possible extensions we are importing, or
specific filenames for cases where a file doesn't have an extension.
This process is getting tedious given the amount of source we are sharing.

Looking for any tips on what I might be doing wrong, or if there's a
better way to handle this.

Brian