Loss of non ascii characters from QString to char *












0















I have a QString with non ascii characters . I am passing this QString to another process . However when I debug the receiving process the argv arguments do not receive a correct string that was intended from the source . My pseudo code would be



process.start( proc, QStringList() << "-a" <<param );
process.waitForFinished(m_timeout);


Here param is the QString that contains the non ascii text










share|improve this question























  • Which OS is this? Encoding of process parameters typically depends on your environment and the application in question.

    – Botje
    Nov 22 '18 at 7:12











  • windows 7 64 bit

    – sameer karjatkar
    Nov 22 '18 at 7:14











  • Does the program accept non-ASCII parameters outside of Qt? Try running proc -a "....." in a cmd window. If that works, you can try in Qt with process.setNativeArguments().

    – Botje
    Nov 22 '18 at 7:16











  • even thru command prompt if i pass the string ,in the debugger of the process I do not get the correct characters

    – sameer karjatkar
    Nov 22 '18 at 7:21











  • Then the problem is on the receiving application. You should make a new question about that.

    – Botje
    Nov 22 '18 at 7:58
















0















I have a QString with non ascii characters . I am passing this QString to another process . However when I debug the receiving process the argv arguments do not receive a correct string that was intended from the source . My pseudo code would be



process.start( proc, QStringList() << "-a" <<param );
process.waitForFinished(m_timeout);


Here param is the QString that contains the non ascii text










share|improve this question























  • Which OS is this? Encoding of process parameters typically depends on your environment and the application in question.

    – Botje
    Nov 22 '18 at 7:12











  • windows 7 64 bit

    – sameer karjatkar
    Nov 22 '18 at 7:14











  • Does the program accept non-ASCII parameters outside of Qt? Try running proc -a "....." in a cmd window. If that works, you can try in Qt with process.setNativeArguments().

    – Botje
    Nov 22 '18 at 7:16











  • even thru command prompt if i pass the string ,in the debugger of the process I do not get the correct characters

    – sameer karjatkar
    Nov 22 '18 at 7:21











  • Then the problem is on the receiving application. You should make a new question about that.

    – Botje
    Nov 22 '18 at 7:58














0












0








0








I have a QString with non ascii characters . I am passing this QString to another process . However when I debug the receiving process the argv arguments do not receive a correct string that was intended from the source . My pseudo code would be



process.start( proc, QStringList() << "-a" <<param );
process.waitForFinished(m_timeout);


Here param is the QString that contains the non ascii text










share|improve this question














I have a QString with non ascii characters . I am passing this QString to another process . However when I debug the receiving process the argv arguments do not receive a correct string that was intended from the source . My pseudo code would be



process.start( proc, QStringList() << "-a" <<param );
process.waitForFinished(m_timeout);


Here param is the QString that contains the non ascii text







c++ qt utf-8






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 6:18









sameer karjatkarsameer karjatkar

90531234




90531234













  • Which OS is this? Encoding of process parameters typically depends on your environment and the application in question.

    – Botje
    Nov 22 '18 at 7:12











  • windows 7 64 bit

    – sameer karjatkar
    Nov 22 '18 at 7:14











  • Does the program accept non-ASCII parameters outside of Qt? Try running proc -a "....." in a cmd window. If that works, you can try in Qt with process.setNativeArguments().

    – Botje
    Nov 22 '18 at 7:16











  • even thru command prompt if i pass the string ,in the debugger of the process I do not get the correct characters

    – sameer karjatkar
    Nov 22 '18 at 7:21











  • Then the problem is on the receiving application. You should make a new question about that.

    – Botje
    Nov 22 '18 at 7:58



















  • Which OS is this? Encoding of process parameters typically depends on your environment and the application in question.

    – Botje
    Nov 22 '18 at 7:12











  • windows 7 64 bit

    – sameer karjatkar
    Nov 22 '18 at 7:14











  • Does the program accept non-ASCII parameters outside of Qt? Try running proc -a "....." in a cmd window. If that works, you can try in Qt with process.setNativeArguments().

    – Botje
    Nov 22 '18 at 7:16











  • even thru command prompt if i pass the string ,in the debugger of the process I do not get the correct characters

    – sameer karjatkar
    Nov 22 '18 at 7:21











  • Then the problem is on the receiving application. You should make a new question about that.

    – Botje
    Nov 22 '18 at 7:58

















Which OS is this? Encoding of process parameters typically depends on your environment and the application in question.

– Botje
Nov 22 '18 at 7:12





Which OS is this? Encoding of process parameters typically depends on your environment and the application in question.

– Botje
Nov 22 '18 at 7:12













windows 7 64 bit

– sameer karjatkar
Nov 22 '18 at 7:14





windows 7 64 bit

– sameer karjatkar
Nov 22 '18 at 7:14













Does the program accept non-ASCII parameters outside of Qt? Try running proc -a "....." in a cmd window. If that works, you can try in Qt with process.setNativeArguments().

– Botje
Nov 22 '18 at 7:16





Does the program accept non-ASCII parameters outside of Qt? Try running proc -a "....." in a cmd window. If that works, you can try in Qt with process.setNativeArguments().

– Botje
Nov 22 '18 at 7:16













even thru command prompt if i pass the string ,in the debugger of the process I do not get the correct characters

– sameer karjatkar
Nov 22 '18 at 7:21





even thru command prompt if i pass the string ,in the debugger of the process I do not get the correct characters

– sameer karjatkar
Nov 22 '18 at 7:21













Then the problem is on the receiving application. You should make a new question about that.

– Botje
Nov 22 '18 at 7:58





Then the problem is on the receiving application. You should make a new question about that.

– Botje
Nov 22 '18 at 7:58












1 Answer
1






active

oldest

votes


















0














I solved the problem with the following code



LPWSTR *szArglist;
int argC;
szArglist = CommandLineToArgvW(GetCommandLineW(),&argC);
if(NULL==szArglist) {
throw;
}
QString qstrConvertFile = QString::fromUtf16((const ushort*)(szArglist[4]));





share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53424921%2floss-of-non-ascii-characters-from-qstring-to-char%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I solved the problem with the following code



    LPWSTR *szArglist;
    int argC;
    szArglist = CommandLineToArgvW(GetCommandLineW(),&argC);
    if(NULL==szArglist) {
    throw;
    }
    QString qstrConvertFile = QString::fromUtf16((const ushort*)(szArglist[4]));





    share|improve this answer




























      0














      I solved the problem with the following code



      LPWSTR *szArglist;
      int argC;
      szArglist = CommandLineToArgvW(GetCommandLineW(),&argC);
      if(NULL==szArglist) {
      throw;
      }
      QString qstrConvertFile = QString::fromUtf16((const ushort*)(szArglist[4]));





      share|improve this answer


























        0












        0








        0







        I solved the problem with the following code



        LPWSTR *szArglist;
        int argC;
        szArglist = CommandLineToArgvW(GetCommandLineW(),&argC);
        if(NULL==szArglist) {
        throw;
        }
        QString qstrConvertFile = QString::fromUtf16((const ushort*)(szArglist[4]));





        share|improve this answer













        I solved the problem with the following code



        LPWSTR *szArglist;
        int argC;
        szArglist = CommandLineToArgvW(GetCommandLineW(),&argC);
        if(NULL==szArglist) {
        throw;
        }
        QString qstrConvertFile = QString::fromUtf16((const ushort*)(szArglist[4]));






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 23 '18 at 12:24









        sameer karjatkarsameer karjatkar

        90531234




        90531234
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53424921%2floss-of-non-ascii-characters-from-qstring-to-char%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

            ComboBox Display Member on multiple fields

            Is it possible to collect Nectar points via Trainline?