Delphi project -- convert to unicode
Bids
24
Avg Bid
$1483 USD
Project ID:
555376
Project Type:
Fixed
Budget:
N/A
Project Description:
I have 10 MB of Delphi (2006) source code that includes compiled and non-compiled units. The code is well-organised and is used to produce some text-analysis software programs. The source code includes different definitions of string types and I wish to convert them so that I have unicode versions of the software. The attached file shows the basic functionality of the software.
Skills required:
Delphi
Additional Files:
tour.pdf
Public Clarification Board
11 messages
-
I am getting more info on what will be involved in converting the code to unicode in Delphi 2009/2010. I may cancel this project and re-post it with new and more detailed info. When I first posted the project, the contents of the source code were unknown to me and my original statements about it
have obviously been misleading.
over 2 years ago
-
It seems that this project was originally conceived in Delphi 1,2 or 3.
A blind man can see this,just looking at the src code, posted.
It can not be compiled with any of the 200x versions of Delphi !
It would make no sense at all to convert this project into anything but
Delphi
2009++.(2006/7 make no sense)
Since there are almost 200 src files adding up to over 3 Mb.
Alas this will take >50 hours,to do it right.
I need to see more of the code !Could you not zip al the stuff up and put
it online so one can have a clearer idea of what is
required.
Regards Pascal
over 2 years ago
-
I may not have loaded the right component. I am checking with the original programmer to see whether there are 3rd components that need to be loaded into 2010
over 2 years ago
-
I ran the syntax check in Delphi 2010 for shared code for two of the programs. The list of errors is shown in the attached Word doc
Attachment:
delphiscreen.doc
over 2 years ago
-
I should say that I am looking for a long-term relationship. The code that I have is clean and well-commented. I want to move forward and do the conversion to unicode (this project) and then develop the software further after that. It is no use to me to get the unicode version but then have a jumble
of messy code. I will be looking for good coding practices.
over 2 years ago
-
There are 197 pas files. Total size is 3.05 MB
over 2 years ago
-
Please ignore my comment about compiled units. I only meant that the 10MB included the exec files. The source code is good Delphi code. I will attach one unit, which covers text search, the core of the program.
Attachment:
SRCHCTX.PAS
over 2 years ago
-
Thanks for the details.
Which flavor of Delphi 2010 will be needed and are you able to supply the needed Delphi 2010 version ?
over 2 years ago
-
Thanks for your comments. I would aim to move to Delphi 2010. As far as I am aware, there are no 3rd party components. The exception might be some code for expiration on one of the products. (That is not important and can be skipped.) I have been selling some software, mainly 3 programs that are
compiled from the code, for several years. A programmer has recently produced a simplified version of the software from the source code.
over 2 years ago
-
Can you clarify if the source code (in it's current state) is complete and can actually be compiled in Delphi 2006 into a working program?
Is this Delphi 2006 program use any 3rd party or open source components? If so, are they identified and will they be provided?
My concern is I
start this project only to find the code is not complete or has missing units or components that are unknown. Then I would end up spending unexpected days of work to track down, acquiring, installing, and configuring these components.
Any details would be helpful.
over 2 years ago
-
Question: What was your planned targeted Delphi Version???
If you goal is to support Unicode Strings in version 2007, then why not convert to Delphi 2009/2010. This is the easiest way to convert a Delphi 2006/2007 Application. The new versions provide enhanced warnings when you import the
project into Delphi 2009/2010 which forces support for Unicode and AnsiString. The warnings show which strings and arguments/parameters that need to be examined and corrected.
Another thing to keep in mind are where Sizeof and Length of Strings are used as they are no longer the same length
when using Unicode characters.
Upgrading to the newer version means you will only have to do the Unicode support once with this conversion and not again when you do decide to upgrade to Delphi 2009 or higher in the future.
Brooks Vaughn
Delphi 2009/2010 uses Unicode Strings and
the WideStrings from 2007 would have to
over 2 years ago