bugPSPP - Bugs: bug #42193, difference between syntax and...


bug #42193: difference between syntax and dictionary encoding is confusing

Submitter:  Ben Pfaff <blp>
Submitted:  Fri 25 Apr 2014 04:08:58 AM UTC
Category:  Internationalization/Localization Severity:  5 - Average
Status:  None Assigned to:  None
Open/Closed:  Open Release:  None
Effort:  0.00
* Mandatory Fields

Add a New Comment Rich Markup

Fri 25 Apr 2014 04:08:58 AM UTC, original submission:  

The ability to have different encoding for syntax files and dictionaries is meant to be helpful, and it often is.  For example, it makes sense to be able to read a system file encoded in an arbitrary encoding from a syntax file encoded in some other encoding.

However, there is considerable room for confusion when using the --syntax-encoding command line option: if the syntax file in question creates a new dictionary, then the encoding for that dictionary doesn't follow from the syntax file's encoding, even though one would naively expect it to do so.  Instead, the new dictionary's encoding follows independently from SET LOCALE or the system locale.

I am not sure of a good solution, but it seems a problem worth considering.

Originally encountered: http://lists.gnu.org/archive/html/pspp-users/2014-04/msg00002.html
Problem explained: http://lists.gnu.org/archive/html/pspp-users/2014-04/msg00004.html

Ben Pfaff <blp>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by blp (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code