# Unicode followup - March 3, 2017

**URL:** <https://clarionhub.com/t/unicode-followup-march-3-2017/1057>\
**Category:** clarionsharp.com/blog/\
**Created:** [March 5, 2017, 1:15am UTC](https://clarionhub.com/t/unicode-followup-march-3-2017/1057 "2017-03-05T01:15:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![brahn](https://clarionhub.com/user_avatar/clarionhub.com/brahn/32/756_2.png) [@brahn](https://clarionhub.com/u/brahn)\
**Post date:** [March 5, 2017, 1:15am UTC](https://clarionhub.com/t/unicode-followup-march-3-2017/1057/1 "2017-03-05T01:15:13Z")

</div>

# Unicode followup

> There was a question raised regarding what the new implementation of Unicode support would mean for developers who create Clarion add-on products. The question was asked:

> > Does having THREE encoding options mean every 3rd party product will need to include 3 DLL/DLL and 3 LIB/LIB libraries?

> And the short answer is NO, no need for that. Read on for more details.  
> – [http://clarionsharp.com/blog/unicode-followup/](http://clarionsharp.com/blog/unicode-followup/)