Getting errors like this when burning non-English subtitles? [Parsed_subtitles_0 @ 0x561d3a0b3b80] Glyph 0x6709 not found, selecting one more font for (Sans, 700, 0) [Parsed_subtitles_0 @ 0x561d3a0b3b80] Glyph 0x4E9B not found, selecting one more font for (Sans, 700, 0) [Parsed_subtitles_0 @ 0x561d3a0b3b80] Glyph 0x4EBA not found, selecting one more font for (Sans, 700, 0) [Parsed_subtitles_0 @ 0x561d3a0b3b80] Glyph 0x505A not found, selecting one more fon........

find /usr/share/zoneinfo/|sed s#"/usr/share/zoneinfo/"##g|grep "/"|grep -v posix|grep -v ^"Etc/"|grep -v ^right|grep -v ^"SystemV" Africa/Addis_Ababa Africa/Abidjan Africa/Blantyre Africa/Lusaka Africa/Casablanca Africa/Libreville Africa/Asmara Africa/Bujumbura Africa/Dakar Africa/Lagos Africa/Malabo Africa/Harare Africa/Kigali........

I bought the 1TB Deskstar C revision recently at just $49 each and put them in RAID 1for my Desktop. Look at how close the old Deskstar 1TB comes to matching the performance of the mor expensive Samsung and WD's? This is phenomal, I can't believe the performance I've gotten out of these cheap drives. http://www.tomshardware.com/reviews/hitachi-western-digital-terabyte,2017-6.html........

http://www.tomshardware.com/news/RAID-5-Doomed-2009,6525.html I found this article interesting, it basically says that with 2TB hard drives or larger sizes, you are more likely to encounter an unrecoverable read error. But is this just another Y2K doomsday? Don't HDD's have enough advanced hardware ECC error and read recovery to prevent this from happening? I'm almost tempted to build a 3 x........