Recent

« previous next »
Pages: [1]

Author Topic: LCL and Unicode  (Read 7130 times)

Anonymous

  • Guest
LCL and Unicode
« on: November 29, 2005, 04:08:27 am »
What are the goals of the LCL in regard to Unicode? Does it aim to be a Unicode capable component suite like the TNT controls across all platforms?
Logged

Marc

  • Administrator
  • Hero Member
  • *
  • Posts: 2649
RE: LCL and Unicode
« Reply #1 on: November 29, 2005, 11:59:35 am »
Unicode is supported by means of UTF8. For now on widgetset which support it. On linux, if you have set your LANG to something .utf8, all controls use utf8 as encoding.
So unlike Delhpi there is no separate widgetset needed
Logged
//--
{$I stdsig.inc}
//-I still can't read someones mind
//-Bugs reported here will be forgotten. Use the bug tracker

Anonymous

  • Guest
RE: LCL and Unicode
« Reply #2 on: January 06, 2006, 12:18:36 pm »
UTF-8 sounds great, but TNT goes beyond visual components... what about ExtractFilePath etc.? FindFirst/FindNext results? Are they already UTF-8 strings?
Logged

Anonymous

  • Guest
RE: LCL and Unicode
« Reply #3 on: March 28, 2006, 02:04:06 pm »
no, it cannot be Unicode if u do not rewrite its interface
Logged

felipemdc

  • Administrator
  • Hero Member
  • *
  • Posts: 3538
RE: LCL and Unicode
« Reply #4 on: March 28, 2006, 09:41:11 pm »
> no, it cannot be Unicode if u do not rewrite its interface

I think that everything on the Free Pascal Run-time library works for UTF-8.

Otherwise, it would be impossible to write utf-8 software with Lazarus, because they use the Run-time library a for string operations, and I'm pretty sure that utf-8 software can be written with Lazarus.
Logged
Pages: [1]
« previous next »
 

TinyPortal © 2005-2018