Announcement

Collapse
No announcement yet.

Wrong compare output

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wrong compare output

    Hello,

    I'm comparing files via Text-Compare. We files contains PCL-Code in plaintext format.
    In the most cases it works fine and the results are good, but in some examples it doesn't.

    Here is one of these examples:

    File 1:
    &l6.5C(19U(s1p9v0b0s16602T*p219X€ 1.022.583,76 some text, 51.129,19 some text

    File 2:
    &l6.5C(19U(s1p9v0b0s16602T*p219X€ 1.022.583,76 some text, 51.129,19 some text

    This files are made in we same way. If I start a Text-Compare (via Scripting ) for this files, I get the following result:

    Code:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <bcreport created="11.03.2016 10:57:21">
    	<ltpath/>
    	<rtpath/>
    	<filecomparison created="11.03.2016 10:57:21">
    		<filename1>C:\Program Files\Beyond Compare 4\report_test\muster\61.prt</filename1>
    		<filename2>C:\Program Files\Beyond Compare 4\report_test\aktuell\61.prt</filename2>
    		<mode>Unterschiede</mode>
    		<linecomp status="different">
    			<text ltid="1">&amp;l6.5C(19U(s1p9v0b0s16602T*p219X€ 1.022.583,76 some text,  51.129,19 some text</text>
    			<text rtid="1">&amp;l6.5C(19U(s1p9v0b0s16602T*p219X? 1.022.583,76 some text, ? 51.129,19 some text</text>
    		</linecomp>
    	</filecomparison>
    </bcreport>
    It seems Beyond Compare doesn't get the € right in the right text-file.
    In others files the problem appears with the character: •

    example:
    File 1:
    und b)• VGB</text>

    File 2:
    und b)? VGB</text>


    Seems maybe like an encoding problem to me, but as I said the files are generated in the same way. What do you think?

    regards,
    phil


    - Edit -
    I checked both files and the hex-view seems identically:

    File 1:
    plaintext:
    pauschal für Personen- und Sachschäden, €

    hex:
    70 61 75 73 63 68 61 6C 20 66 FC 72 20 50 65 72 73 6F 6E 65 6E 2D 20 75 6E 64 20 53 61 63 68 73 63 68 E4 64 65 6E 2C 20 80

    File 2:
    plaintext:
    pauschal für Personen- und Sachschäden, €

    hex:
    70 61 75 73 63 68 61 6C 20 66 FC 72 20 50 65 72 73 6F 6E 65 6E 2D 20 75 6E 64 20 53 61 63 68 73 63 68 E4 64 65 6E 2C 20 80
    Last edited by phil; 11-Mar-2016, 08:17 AM.

  • #2
    Hello,

    Thanks for the detailed example case.

    If you load the two files into a new, blank Text Compare, which symbols do you see? The auto-detected encoding is displayed at the top of the status bar for each individual pane: what is it currently detecting as?

    And are you running the latest BC 4.1.4 release?
    Aaron P Scooter Software

    Comment


    • #3
      Hello,

      I tested it via GUI, BC detected the same encoding and the character seems to be okay:

      Encoding Screenshot:
      http://www.directupload.net/file/d/4...45u6wg_png.htm

      Example Row:
      http://www.directupload.net/file/d/4...tmq64v_png.htm

      I'm using BC 4.1.2 right now.

      Comment


      • #4
        Hello,

        I generally recommend updating to the latest release (4.1.4 in this case).

        You can create a portable install to a global location (c:\tools\Beyond Compare 4\). This would guarantee that the GUI and script are using the same settings, which are otherwise stored per user account.
        If you create a Portable Install, and re-test in the GUI, does the encoding detect correctly? This includes the step of generating the Text Report from the Session menu -> Text Compare Report.
        If you then use this Portable Install for your scripting, does it then also detect encoding correctly?
        Aaron P Scooter Software

        Comment

        Working...
        X