MS Project Export as CSV not generating non english language data
i have been following below link to save MS Project file as CSV https://support.microsoft.com/en-us/office/export-or-import-data-to-another-file-format-6e6e581f-a580-4f04-aa87-9b6552143d9c#:~:text=Choose%20File%20%3E%20Save%20As.%20Choose%20Browse.%20In,a%20name%20for%20the%20exported%20file.%20Choose%20Save%EF%BF%BC%EF%BF%BCi using Existing Task Export Map to save as CSV Issue i am facing is after generating CSV, non English data is getting corrupted, showing as "????????" in the CSV CSV File generated is getting saved as ANSI encoding, there is no way to change it to UTF 8 in Export Wizard these are all steps can be done Mannully on MS Project i also have MSPPlugin written in DotNet which does same exact steps programmatically have used below APIs to perform the same https://learn.microsoft.com/en-us/office/vba/api/project.application.mapedit https://learn.microsoft.com/en-us/office/vba/api/project.application.filesaveas getting same output as shown in screenshot Note: I have MS Project Standard 2019 installed on windows
CSV file size from "Save Results As..." versus exported via SSIS Package / Export Wizard
When exporting query results from the grid using "Save Results As...", I'm consistently creating CSV files that are half the size of CSV files created by exporting via the Import/Export Wizard (and the resulting SSIS Package). Exact same query used for both, same results, same number of records etc. I believe this has to do with the file encoding used by each export process. I know this is not a precise science, but based on how Notepad interprets the resulting files, the encoding of the "Save Results As..." files is "UTF-8 with BOM", while the SSIS Package generates a "UTF-16 LE" file. I've tried a variety of approaches to try to get the Import / Export Wizard to mimic the "Save Results As" encoding without success. Changing the Code Page field on the "Choose a Destination" screen to "65001 (UTF-8)" results in the dreaded "DT_NTEXT not supported with ANSI files" error upon export due to nvarchar(max) data types in the source table. That can be resolved by checking the Unicode box on the "Choose a Destination" page, but checking Unicode also disables the Code Page dropdown. Even if you select "65001 (UTF-8)" in Code Page and then check Unicode, it still produces a UTF-16 encoded file. Two questions at this point: 1) How does the "Save Results As..." function in the query grid avoid the DT_NTEXT error and produce a UTF-8 encoded file? 2) If I tried to edit the package in SSIS Designer, would I have more control over the encoding and be able to mimic the "Save Results As..." file sizes? This would take a bit of effort (installing Visual Studio data tools, learning how to use it, etc) so if that's a dead end I'd rather not pursue it.
