krahllucas / pborca Goto Github PK

What steps will reproduce the problem?

1. pborcaa export.orc

2. File export.orc:

session begin pborc90.dll
export angel.pbl, , ,
session end


What is the expected output? What do you see instead?
  export.orc (19) : Buffer size for 'w_aperturar_angel' is insufficent


What version of the product are you using? On what operating system?
  1.00.17


Please provide any additional information below.
  Object causes Crahs, has embedeed BINARY DATA at the end of object
  'w_aperturar_angel'.

  The Object Embedded Binary Data As an OleObject Control.


NOTE: PBNAtive Work Correclty, and C# using pborcaxx.dll Work Ok.

Thanks!!

Jordi Gonzalez Gonzalez

What steps will reproduce the problem?
1. Export files to a folder
2. Make a folder named SOURCE under folder
3. pborca testexport.bat.orc

What is the expected output? What do you see instead?
The file is ANSI encoded.

I expect that the first line of the exported file to be
$PBExportHeader$generic_pfc_app.sra

This is the first line.
HA$PBExportHeader$generic_pfc_app.sra

What version of the product are you using? On what operating system?
pborca.exe dated 7-03-10 18:37:06

Please provide any additional information below.

What steps will reproduce the problem?
1. Pick any file containing a character outside of ASCII range (0-127) followed 
by one or more whitespace characters inside ASCII range (like horizontal tab, 
space, newline)
2. Export the file using the export command

What is the expected output? What do you see instead?

Besides creating HEXASCII "tags" for contiguous sequences of non-ASCII 
characters PowerBuilder also includes whitespace characters after the non-ASCII 
one(s) into the tag, but pborca doesn't.

The string below:

Demodé IDE

Is exported by PowerBuilder (with HEXASCII encoding, the only encoding 
available when using PB with source control plugin) as:

Demod$$HEX2$$e9002000$$ENDHEX$$IDE

And pborca exports it as:

Demod$$HEX1$$e900$$ENDHEX$$ IDE

Introducing a lot of differences in source code if you develop non-English 
software and integrate pborca into your source code management workflow.

I've developed some Python code to fix a workspace after exporting its sources 
using pborca and the results are pretty good, although I'm not 100% sure it's 
equal to the results PB would yield itself.

The code below basically uses regular expressions to find occurrences of the 
tags that would be encoded differently by PB and includes the whitespace after 
them, then it merge two tags without any characters between them into one tag 
until there's nothing to include or merge. I hope you understand Python.

            with open(path) as f:
                content = f.read()

            n = True
            while n:
                content, i = _ha_whitespace_re.subn(_ha_whitespace, content)
                content, j = _ha_merge_re.subn(_ha_merge, content)
                n = i + j

            with open(path, 'w') as f:
                f.write(content)

What version of the product are you using? On what operating system?

pborca 1.00.17

Along with PowerBuilder Enterprise:
 - version 10.5 build 5063
 - version 11.2 build 9097

Please provide any additional information below.

What steps will reproduce the problem?
1. Pick any source file (*.sr?) containing escape sequences (like ~r~n) on the 
same line as $PBExportComments$
2. Use import command to import this file into a PBL

What is the expected output? What do you see instead?

Expected: the line breaks are displayed as line breaks in the object properties 
window and if you export the object using PowerBuilder the comment line is the 
same as the imported file.

Actual behavior: the line breaks are displayed as ~r~n in the object properties 
window and if you export the object using PowerBuilder the comment line 
contains two tildes for every tilde present in the imported file. Example:

The input file contains:

$PBExportComments$Line~r~nbreak.

The property window of this object will display the comment as:

Line~r~nbreak.

And when the file is exported using PowerBuilder the same line will contain:

$PBExportComments$Line~~r~~nbreak.

This is inoffensive, but is specially annoying when you integrate pborca in 
your source control workflow because PowerBuilder acts as if you have modified 
the object when you didn't, you just imported the unmodified file into the PBL.

What version of the product are you using? On what operating system?

pborca 1.00.17

Along with PowerBuilder Enterprise:
 - version 10.5 build 5063
 - version 11.2 build 9097

Please provide any additional information below.

This is required since the following issue in pbscc:
http://code.google.com/p/pbscc-proxy/issues/detail?id=3

Now pbscc could convert file encoding from HEXASCII to UTF-8 before commit into 
SVN.