How to change the default encoding used by pbscc's functions

[GoogleCodeExporter]

What steps will reproduce the problem?
When chosing 'Add To Source Control...' in powerbuilder to add a object to 
source control, the source file of the object is encoded using HEXASCII. 
If the source of the object is writed in English, it is OK. But if the source 
of the object has some comments in Chinese, the output file encoded using 
HEXASCII is unreadable to Chinese characters.

The version of the pbscc I'm  using is pbsccsetup_2.00.33.
What do you see instead, and how to solve the problem?

Please provide any additional information below.

Original issue reported on code.google.com by Koup...@gmail.com on 19 Jun 2010 at 2:10

[GoogleCodeExporter]

The exported files are generated by PowerBuilder itself.
So, the only way to recode to utf-8 before put into svn.
Not so complicated to implement...
Ready to pay? ;-)

Original comment by daggett....@gmail.com on 21 Jun 2010 at 6:53

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I know the exported files are generated by PowerBuilder intselt.
But I think that it is the PBSCC function tell PowerBuilder to do so.
When the PBSCC function tell PowerBuilder to export some file,
does the function tell PowerBuilder to choose what Encoding?
If the function has nothing to do with the encoding, then I don't think the 
function
is perfect.
I try to find the configuration for the default export encoding in 
PowerBuilder，
I find the configuration in PB.ini file. But after setting the enconding i just 
need,
but it still doesn't work.
Yes,it's too complicated to recode to utf-8 before put into svn.
Do you really have some simple way to get my goal?

Sorry for my English.

Original comment by Koup...@gmail.com on 23 Jun 2010 at 7:01

[GoogleCodeExporter]

It's PowerBuilder who exports file and asks SCC provider (PBSCC) to save it 
into storage (SVN).
--
Yes, I know how to decode HEXASCII and 
I know how to encode it in UTF-8
--
Do you really need it?

Original comment by daggett....@gmail.com on 23 Jun 2010 at 4:50

[GoogleCodeExporter]

Of course, I need it.
Ready to pay? Are you kidding?

Original comment by Koup...@gmail.com on 24 Jun 2010 at 3:21

[GoogleCodeExporter]

I just published new version 2.0.43 where this feature is available.
Add the following line into scc.ini

export.encoding=utf-8

Original comment by daggett....@gmail.com on 28 Jun 2010 at 4:03

• Changed state: Fixed

[GoogleCodeExporter]

PS: after this change I have to add utf-8 support for the 
http://code.google.com/p/pborca

Original comment by daggett....@gmail.com on 29 Jun 2010 at 10:39

[GoogleCodeExporter]

 Thank you very much increased "recode to utf-8" of the function
 I found a bug, The reason is there '$$$HEX' rather than '$$HEX'.

Original comment by wop...@gmail.com on 29 Jul 2010 at 10:48