Draft of New Practical Unicode Section for FAQ or Perl Doc.#118
Draft of New Practical Unicode Section for FAQ or Perl Doc.#118brainbuz wants to merge 1 commit intoperl-doc-cats:masterfrom
Conversation
|
A lot of things don't make sense about this. I can't spare the time to review in depth but a few of these would probably be better added to perlunifaq and a few are wrong. |
|
Anything in this distribution needs to be in perlfaq* pod documents only. |
|
@Grinnz this is a starting point, and if I'm getting things wrong, it only underlines the gap I'm trying to cover. Hopefully some of the other maintainers will have some time to help. I've also converted to a github draft since it's not nearly ready for a merge. |
|
I like the idea of a question like "What does 'Wide character in print' mean?", as the answer isn't always obvious. The answer in perlfaq itself could be short, if there is an appropriate paragraph in perlunifaq that can be linked to, and we can also include a reminder that the |
The answers to the practical issues arising from the way Perl handles unicode are not in a convenient section. I've written a few faq formatted items to address the topic: How do I get rid of Wide Character in Print and Garbled Unicode? In this pull request it's a new topic for the perlfaq (which if you agree that's best would probably become perlfaq10), it would also make sense as an addition to the Core Documentation unicode faq, or you might prefer to add it to one of the other faq sections. There are probably more tips that would fit this, if you want to suggest them. Every time I hit a unicode issue I end up chasing my tail looking for the solution, putting the answers together in a faq section would make it so much easier.