Tagging boolean boxes on cover pageAnswered
You are correct, its that pesky Windows 10 that is causing the issue. And you are also correct that the using Wingdings font previously allowed you to address the issue, but with the XBRL requirement, that wouldn't be an acceptable format for tagging these checkboxes. There are two options for you to be able to keep them tagged correctly and make them visible to Windows 10 users.
- Save the file as PDF (Beta) and send that for review
- Have the user(s) with Windows 10 download and install the font Arial Unicode MS*
*Note that in order to download and install the font, they'd need to either a) purchase the font (https://www.fonts.com/font/monotype/arial-unicode), or b) have someone with the font download and send it to them.
In this case, you have the font on your machine, so it would be possible for you to send them the font to install. If needed, your IT team may be able to assist here too.
Sorry I couldn't be of more help. Let me know what questions you have for me in the meantime. Have a great day otherwise and chat with you soon.0
I guess I was misunderstanding this before. We must use the check box character included in the Workiva cover tagging template or the tag won't be accepted when filed?
I'm not sure if anyone in my company still has a Windows version below 10. How can they expect companies to purchase a special font for one tag of iXBRL? :(0
I realize my above statement is a bit misleading, so I'm happy to help clarify for you as best I can.
For the specific cover page tags that require True/False Facts, i.e. boolean checkboxes, they require specific unicode characters to transform correctly when they are tagged and then submitted. You are correct that if they are tagged with a non-conforming checkbox type (like Wingdings), you'll get an error which would prevent a filing.
While the checkboxes supplied in the templates provided by Workiva do contain the correct boolean types, you can also add these directly by using the font Arial Unicode MS, which was added to Wdesk via the Insert > Symbol menu.
Since the Wdesk application both supports the unicode characters plus has the appropriate font, you'd still be able to tag these values correctly either by copying and pasting from the template or inserting from the menu in Wdesk. This is for or any user, either on Windows 10, Windows 7, or other. The only catch for Windows 10 users is when you perform the copy/paste method from the template, you wouldn't see the boxes correctly because you wouldn't have the font needed. Other OS systems do have the font, though. However, using the Insert > Symbol method would work for Windows 10 users. Does that make sense?
Hope that helps alleviate some confusion there. Do let me know if you have any follow-ups or need anything else. Thanks as always and have a most excellent day in the meantime. Cheers!0
Aha! I understand now. I think your second explanation is what I thought I understood from before and then I misunderstood your first comment here. Excellent! I'll do the insert and hopefully, we'll be all set.
Also, I LOVE your moving graphic to show the steps! Too cool!0
No problem! After rereading, I can see how its a bit confusing, so my bad there.
And glad you like the gif. Its the small things ;)0
Edit: I am so sorry! I turned XBRL off and the check box showed up in the document! I didn't think to try that. Please disregard the below.
So, maybe I misunderstood again. I followed your steps above to insert a new Arial Unicode MS check box into the first table that contains the "QUARTERLY REPORT PURSUANT..." statement. However, I'm still seeing an empty box.
iXBRL likes it now, but it's still looks blank. I did print to PDF and see that the check box shows up there.0
Snap! Clear as mud, it seems ;)
Thanks for reaching out. I'll do some digging here and get back to you.0
I am re-reading your above comment and it seems like toggling XBRL resolved for you? Let me know if that's not the case or you need anything else.0
Yes, that's correct. After I left my post, I went back to Wdesk, to move on to something else, and when I turned off XBRL, the check box became visible. I tried to come back and edit the post quick enough to keep you from researching further. :)
Management rarely ever looks at the documents with XBRL on, so my only concern was back when the check box was invisible with XBRL off. Naturally, the first directed comment left by my manager in our 10-Q was "what happened to the check box?"
Long story short, I think I'm all set on this now. Thanks for all your help!0
Please sign in to leave a comment.