Is hiragana equal to lower case and katakana equal to upper case when comparing Japanese and western writing...












2














In western languages, if we need to emphasize some words, or mark something to be special, we use ALL UPPER CASE to do that even when the word is normally written with lower case. While in Japanese, we can write that word in katakana even when the word is normally written with hiragana.



Does this fact mean, when doing computer programming, we can treat hiragana as a lower case letter, and katakana as an upper case letter. For example, are the following algorithms appropriate for a Japanese user?




  • A procedure converting a sentence to all upper case converts all hiragana characters to katakana inside, and a procedure converting a sentence to all lower case converts all katakana characters to hiragana chracters.

  • When naming variables in camelCase, if the variable name is in Japanese, use a katakana at the beginning of a word, and a hiragana otherwise

  • In terms of password complexity requirement, e.g. at least 1 upper case and 1 lower case, count hiragana as lower case and katakana as upper case when the user enters Japanese as password.










share|improve this question







New contributor




Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Is it even possible to use hiragana and katakana in passwords? Considering that they are most typically entered using romaji.
    – Leebo
    1 hour ago










  • for most major programming languages, the code is written using the roman alphabet, so most of your analogy is moot.
    – virmaior
    1 hour ago
















2














In western languages, if we need to emphasize some words, or mark something to be special, we use ALL UPPER CASE to do that even when the word is normally written with lower case. While in Japanese, we can write that word in katakana even when the word is normally written with hiragana.



Does this fact mean, when doing computer programming, we can treat hiragana as a lower case letter, and katakana as an upper case letter. For example, are the following algorithms appropriate for a Japanese user?




  • A procedure converting a sentence to all upper case converts all hiragana characters to katakana inside, and a procedure converting a sentence to all lower case converts all katakana characters to hiragana chracters.

  • When naming variables in camelCase, if the variable name is in Japanese, use a katakana at the beginning of a word, and a hiragana otherwise

  • In terms of password complexity requirement, e.g. at least 1 upper case and 1 lower case, count hiragana as lower case and katakana as upper case when the user enters Japanese as password.










share|improve this question







New contributor




Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Is it even possible to use hiragana and katakana in passwords? Considering that they are most typically entered using romaji.
    – Leebo
    1 hour ago










  • for most major programming languages, the code is written using the roman alphabet, so most of your analogy is moot.
    – virmaior
    1 hour ago














2












2








2







In western languages, if we need to emphasize some words, or mark something to be special, we use ALL UPPER CASE to do that even when the word is normally written with lower case. While in Japanese, we can write that word in katakana even when the word is normally written with hiragana.



Does this fact mean, when doing computer programming, we can treat hiragana as a lower case letter, and katakana as an upper case letter. For example, are the following algorithms appropriate for a Japanese user?




  • A procedure converting a sentence to all upper case converts all hiragana characters to katakana inside, and a procedure converting a sentence to all lower case converts all katakana characters to hiragana chracters.

  • When naming variables in camelCase, if the variable name is in Japanese, use a katakana at the beginning of a word, and a hiragana otherwise

  • In terms of password complexity requirement, e.g. at least 1 upper case and 1 lower case, count hiragana as lower case and katakana as upper case when the user enters Japanese as password.










share|improve this question







New contributor




Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











In western languages, if we need to emphasize some words, or mark something to be special, we use ALL UPPER CASE to do that even when the word is normally written with lower case. While in Japanese, we can write that word in katakana even when the word is normally written with hiragana.



Does this fact mean, when doing computer programming, we can treat hiragana as a lower case letter, and katakana as an upper case letter. For example, are the following algorithms appropriate for a Japanese user?




  • A procedure converting a sentence to all upper case converts all hiragana characters to katakana inside, and a procedure converting a sentence to all lower case converts all katakana characters to hiragana chracters.

  • When naming variables in camelCase, if the variable name is in Japanese, use a katakana at the beginning of a word, and a hiragana otherwise

  • In terms of password complexity requirement, e.g. at least 1 upper case and 1 lower case, count hiragana as lower case and katakana as upper case when the user enters Japanese as password.







katakana hiragana






share|improve this question







New contributor




Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 hours ago









Michael Tsang

1111




1111




New contributor




Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Michael Tsang is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • Is it even possible to use hiragana and katakana in passwords? Considering that they are most typically entered using romaji.
    – Leebo
    1 hour ago










  • for most major programming languages, the code is written using the roman alphabet, so most of your analogy is moot.
    – virmaior
    1 hour ago


















  • Is it even possible to use hiragana and katakana in passwords? Considering that they are most typically entered using romaji.
    – Leebo
    1 hour ago










  • for most major programming languages, the code is written using the roman alphabet, so most of your analogy is moot.
    – virmaior
    1 hour ago
















Is it even possible to use hiragana and katakana in passwords? Considering that they are most typically entered using romaji.
– Leebo
1 hour ago




Is it even possible to use hiragana and katakana in passwords? Considering that they are most typically entered using romaji.
– Leebo
1 hour ago












for most major programming languages, the code is written using the roman alphabet, so most of your analogy is moot.
– virmaior
1 hour ago




for most major programming languages, the code is written using the roman alphabet, so most of your analogy is moot.
– virmaior
1 hour ago










1 Answer
1






active

oldest

votes


















1














No, they are very much different.



Katakana is primarily used for writing foreign loanwords and foreign names, as well as onomatopoeia; mixed hiragana/kanji is used for all else. Writing a sentence all in katakana doesn't sound like SHOUTING, it sounds like the speaker has a foreign accent; mixed kanji and katakana sounds archaic (as that was the convention for certain kinds of official documents pre-1946).



As to your equivalence algorithms, no, it would not be helpful. To answer each point in turn:




  • Converting all hiragana to katakana results in a very odd-looking sentence; one which you might only find in fiction (see above for why). You would never want to convert all katakana to hiragana, as there are many common words that are (nearly) always written with katakana - and converting them to hiragana makes it harder to visually separate them from the surrounding text (since Japanese has no spaces). All-hiragana text at best looks like a children's book, if there are no kanji; all-hiragana, no kanji and no spaces is basically unreadable.


  • Katakana and hiragana are never mixed inside a single word (unless you're going for an ExTremElY sTRanGe eFFEct). There is nothing in Japanese analogous to initial capitalisation.


  • Passwords in actual Japanese script are very rare, and would likely confuse Japanese users more than simply requiring Roman letters. If you did want to allow them, you shouldn't have a requirement to mix hiragana and katakana, largely because of the above reasons. (IMO, you shouldn't require a mix of capitals and lower case in English passwords, as the strongest passwords I use are all lowercase letters and spaces - they're strong by length and very easy to remember - and it's very annoying to have to alter them to meet each site's individual password requirements.)







share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "257"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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
    },
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });






    Michael Tsang is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fjapanese.stackexchange.com%2fquestions%2f64662%2fis-hiragana-equal-to-lower-case-and-katakana-equal-to-upper-case-when-comparing%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









    1














    No, they are very much different.



    Katakana is primarily used for writing foreign loanwords and foreign names, as well as onomatopoeia; mixed hiragana/kanji is used for all else. Writing a sentence all in katakana doesn't sound like SHOUTING, it sounds like the speaker has a foreign accent; mixed kanji and katakana sounds archaic (as that was the convention for certain kinds of official documents pre-1946).



    As to your equivalence algorithms, no, it would not be helpful. To answer each point in turn:




    • Converting all hiragana to katakana results in a very odd-looking sentence; one which you might only find in fiction (see above for why). You would never want to convert all katakana to hiragana, as there are many common words that are (nearly) always written with katakana - and converting them to hiragana makes it harder to visually separate them from the surrounding text (since Japanese has no spaces). All-hiragana text at best looks like a children's book, if there are no kanji; all-hiragana, no kanji and no spaces is basically unreadable.


    • Katakana and hiragana are never mixed inside a single word (unless you're going for an ExTremElY sTRanGe eFFEct). There is nothing in Japanese analogous to initial capitalisation.


    • Passwords in actual Japanese script are very rare, and would likely confuse Japanese users more than simply requiring Roman letters. If you did want to allow them, you shouldn't have a requirement to mix hiragana and katakana, largely because of the above reasons. (IMO, you shouldn't require a mix of capitals and lower case in English passwords, as the strongest passwords I use are all lowercase letters and spaces - they're strong by length and very easy to remember - and it's very annoying to have to alter them to meet each site's individual password requirements.)







    share|improve this answer




























      1














      No, they are very much different.



      Katakana is primarily used for writing foreign loanwords and foreign names, as well as onomatopoeia; mixed hiragana/kanji is used for all else. Writing a sentence all in katakana doesn't sound like SHOUTING, it sounds like the speaker has a foreign accent; mixed kanji and katakana sounds archaic (as that was the convention for certain kinds of official documents pre-1946).



      As to your equivalence algorithms, no, it would not be helpful. To answer each point in turn:




      • Converting all hiragana to katakana results in a very odd-looking sentence; one which you might only find in fiction (see above for why). You would never want to convert all katakana to hiragana, as there are many common words that are (nearly) always written with katakana - and converting them to hiragana makes it harder to visually separate them from the surrounding text (since Japanese has no spaces). All-hiragana text at best looks like a children's book, if there are no kanji; all-hiragana, no kanji and no spaces is basically unreadable.


      • Katakana and hiragana are never mixed inside a single word (unless you're going for an ExTremElY sTRanGe eFFEct). There is nothing in Japanese analogous to initial capitalisation.


      • Passwords in actual Japanese script are very rare, and would likely confuse Japanese users more than simply requiring Roman letters. If you did want to allow them, you shouldn't have a requirement to mix hiragana and katakana, largely because of the above reasons. (IMO, you shouldn't require a mix of capitals and lower case in English passwords, as the strongest passwords I use are all lowercase letters and spaces - they're strong by length and very easy to remember - and it's very annoying to have to alter them to meet each site's individual password requirements.)







      share|improve this answer


























        1












        1








        1






        No, they are very much different.



        Katakana is primarily used for writing foreign loanwords and foreign names, as well as onomatopoeia; mixed hiragana/kanji is used for all else. Writing a sentence all in katakana doesn't sound like SHOUTING, it sounds like the speaker has a foreign accent; mixed kanji and katakana sounds archaic (as that was the convention for certain kinds of official documents pre-1946).



        As to your equivalence algorithms, no, it would not be helpful. To answer each point in turn:




        • Converting all hiragana to katakana results in a very odd-looking sentence; one which you might only find in fiction (see above for why). You would never want to convert all katakana to hiragana, as there are many common words that are (nearly) always written with katakana - and converting them to hiragana makes it harder to visually separate them from the surrounding text (since Japanese has no spaces). All-hiragana text at best looks like a children's book, if there are no kanji; all-hiragana, no kanji and no spaces is basically unreadable.


        • Katakana and hiragana are never mixed inside a single word (unless you're going for an ExTremElY sTRanGe eFFEct). There is nothing in Japanese analogous to initial capitalisation.


        • Passwords in actual Japanese script are very rare, and would likely confuse Japanese users more than simply requiring Roman letters. If you did want to allow them, you shouldn't have a requirement to mix hiragana and katakana, largely because of the above reasons. (IMO, you shouldn't require a mix of capitals and lower case in English passwords, as the strongest passwords I use are all lowercase letters and spaces - they're strong by length and very easy to remember - and it's very annoying to have to alter them to meet each site's individual password requirements.)







        share|improve this answer














        No, they are very much different.



        Katakana is primarily used for writing foreign loanwords and foreign names, as well as onomatopoeia; mixed hiragana/kanji is used for all else. Writing a sentence all in katakana doesn't sound like SHOUTING, it sounds like the speaker has a foreign accent; mixed kanji and katakana sounds archaic (as that was the convention for certain kinds of official documents pre-1946).



        As to your equivalence algorithms, no, it would not be helpful. To answer each point in turn:




        • Converting all hiragana to katakana results in a very odd-looking sentence; one which you might only find in fiction (see above for why). You would never want to convert all katakana to hiragana, as there are many common words that are (nearly) always written with katakana - and converting them to hiragana makes it harder to visually separate them from the surrounding text (since Japanese has no spaces). All-hiragana text at best looks like a children's book, if there are no kanji; all-hiragana, no kanji and no spaces is basically unreadable.


        • Katakana and hiragana are never mixed inside a single word (unless you're going for an ExTremElY sTRanGe eFFEct). There is nothing in Japanese analogous to initial capitalisation.


        • Passwords in actual Japanese script are very rare, and would likely confuse Japanese users more than simply requiring Roman letters. If you did want to allow them, you shouldn't have a requirement to mix hiragana and katakana, largely because of the above reasons. (IMO, you shouldn't require a mix of capitals and lower case in English passwords, as the strongest passwords I use are all lowercase letters and spaces - they're strong by length and very easy to remember - and it's very annoying to have to alter them to meet each site's individual password requirements.)








        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 1 hour ago

























        answered 1 hour ago









        Sjiveru

        7,2531730




        7,2531730






















            Michael Tsang is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Michael Tsang is a new contributor. Be nice, and check out our Code of Conduct.













            Michael Tsang is a new contributor. Be nice, and check out our Code of Conduct.












            Michael Tsang is a new contributor. Be nice, and check out our Code of Conduct.
















            Thanks for contributing an answer to Japanese Language Stack Exchange!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2fjapanese.stackexchange.com%2fquestions%2f64662%2fis-hiragana-equal-to-lower-case-and-katakana-equal-to-upper-case-when-comparing%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

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            TypeError: fit_transform() missing 1 required positional argument: 'X'