I know it's semantics and I apologize for that but, to be totally correct, TRUNCATE TABLE is actually "FULLY LOGGED" in that it logs all of the pages that it de-allocated. It is not considered to be minimally logged and, yes (just in case someone asks), if used inside a transaction, it can be rolled back. If you look up "Minimally Logged Operations" in Books Online, you won't find TRUNCATE TABLE there.
If you have a database in the Bulk Logged mode, using Truncate won't bother the logfile chain like a minimally logged or bulk logged operation because it's neither and that the real reason to understand that it's not actually minimally logged.
If a logfile backup is taken and the database is in the Bulk Logged mode and no minimally logged operations took place, you can restore to a point in time (PIT) in that log file. If all that is true but a minimally logged operation took place, then you can either restore up to and not including that log file or you can use the whole log file as part of a PIT restore and it can be followed by other log file restores, as well.