A function which translates a sentence to title-caseTitle case name when first, middle and last are all upper or lower caseCounting Words in Files - MATLAB styleFinding the first non-repeating character in a stringCounting words, letters, average word length, and letter frequencyTitle case a sentence functionTest if a string is a palindromeLeetcode 49: Group Anagrams - Hash function design talkAbbreviate a string using dictionary in CTitle Case ConverterGeneric Case Converter

How can bays and straits be determined in a procedurally generated map?

Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?

A Journey Through Space and Time

Has the BBC provided arguments for saying Brexit being cancelled is unlikely?

Can I interfere when another PC is about to be attacked?

How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?

Why don't electron-positron collisions release infinite energy?

How does one intimidate enemies without having the capacity for violence?

Why linear maps act like matrix multiplication?

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

Theorems that impeded progress

Why does Kotter return in Welcome Back Kotter?

Is it possible to make sharp wind that can cut stuff from afar?

Approximately how much travel time was saved by the opening of the Suez Canal in 1869?

What do you call something that goes against the spirit of the law, but is legal when interpreting the law to the letter?

Is there any sparring that doesn't involve punches to the head?

Show that if two triangles built on parallel lines, with equal bases have the same perimeter only if they are congruent.

What do the dots in this tr command do: tr .............A-Z A-ZA-Z <<< "JVPQBOV" (with 13 dots)

Is it possible to rebuild the bike frame (to make it lighter) by welding aluminum tubes

DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?

Email Account under attack (really) - anything I can do?

If I cast Expeditious Retreat, can I Dash as a bonus action on the same turn?

Is it legal for company to use my work email to pretend I still work there?

Why don't electromagnetic waves interact with each other?



A function which translates a sentence to title-case


Title case name when first, middle and last are all upper or lower caseCounting Words in Files - MATLAB styleFinding the first non-repeating character in a stringCounting words, letters, average word length, and letter frequencyTitle case a sentence functionTest if a string is a palindromeLeetcode 49: Group Anagrams - Hash function design talkAbbreviate a string using dictionary in CTitle Case ConverterGeneric Case Converter






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








5












$begingroup$


The task is to write a JavaScript-function which translates a given blank-separated sentence to title-case.



Means that all words shall start with a capital and then the rest of the word in lower-case. But: A certain, specified set of conjunctions, preposition as well as article shall be all lower-case.



Example: "The second of the four items." becomes "The Second of the Four Items.".



Here's my implementation of such a function:






function translateToTitleCase(str) 
const translateWord = (sWord) =>
return sWord.slice(0, 1).toUpperCase() + sWord.slice(1).toLowerCase();


const words = str.split(" ");

words[0] = translateWord(words[0]);

for (let i = 1; i < words.length; i++)
if (!["of", "and", "the", "to"].includes(words[i].toLowerCase()))
words[i] = translateWord(words[i]);
else
words[i] = words[i].toLowerCase(); // Make sure is's the correct case, when the sentence (or parts of it) is given in uppercase.



return words.join(" ");


// -- Examples -------------------------------------------------------------------------------
console.log(translateToTitleCase("Into unmerciful the entreating stronger to of word guessing."));
console.log(translateToTitleCase("the OLD MAN aND THE sEa"));





I think my coding is still a bit "noisy" with the usage of all those brackets, chained methods and concatenation.



Any ideas about how to improve my implementation?



Perhaps some cool new ES6-feature I wasn't aware of.



What would you have done differently and why?










share|improve this question











$endgroup$











  • $begingroup$
    I'd argue that the functionality should be changed slightly – this'll trip over words like xkcd and eBay – but I suppose that's not really in-scope for Code Review.
    $endgroup$
    – wizzwizz4
    44 mins ago


















5












$begingroup$


The task is to write a JavaScript-function which translates a given blank-separated sentence to title-case.



Means that all words shall start with a capital and then the rest of the word in lower-case. But: A certain, specified set of conjunctions, preposition as well as article shall be all lower-case.



Example: "The second of the four items." becomes "The Second of the Four Items.".



Here's my implementation of such a function:






function translateToTitleCase(str) 
const translateWord = (sWord) =>
return sWord.slice(0, 1).toUpperCase() + sWord.slice(1).toLowerCase();


const words = str.split(" ");

words[0] = translateWord(words[0]);

for (let i = 1; i < words.length; i++)
if (!["of", "and", "the", "to"].includes(words[i].toLowerCase()))
words[i] = translateWord(words[i]);
else
words[i] = words[i].toLowerCase(); // Make sure is's the correct case, when the sentence (or parts of it) is given in uppercase.



return words.join(" ");


// -- Examples -------------------------------------------------------------------------------
console.log(translateToTitleCase("Into unmerciful the entreating stronger to of word guessing."));
console.log(translateToTitleCase("the OLD MAN aND THE sEa"));





I think my coding is still a bit "noisy" with the usage of all those brackets, chained methods and concatenation.



Any ideas about how to improve my implementation?



Perhaps some cool new ES6-feature I wasn't aware of.



What would you have done differently and why?










share|improve this question











$endgroup$











  • $begingroup$
    I'd argue that the functionality should be changed slightly – this'll trip over words like xkcd and eBay – but I suppose that's not really in-scope for Code Review.
    $endgroup$
    – wizzwizz4
    44 mins ago














5












5








5


1



$begingroup$


The task is to write a JavaScript-function which translates a given blank-separated sentence to title-case.



Means that all words shall start with a capital and then the rest of the word in lower-case. But: A certain, specified set of conjunctions, preposition as well as article shall be all lower-case.



Example: "The second of the four items." becomes "The Second of the Four Items.".



Here's my implementation of such a function:






function translateToTitleCase(str) 
const translateWord = (sWord) =>
return sWord.slice(0, 1).toUpperCase() + sWord.slice(1).toLowerCase();


const words = str.split(" ");

words[0] = translateWord(words[0]);

for (let i = 1; i < words.length; i++)
if (!["of", "and", "the", "to"].includes(words[i].toLowerCase()))
words[i] = translateWord(words[i]);
else
words[i] = words[i].toLowerCase(); // Make sure is's the correct case, when the sentence (or parts of it) is given in uppercase.



return words.join(" ");


// -- Examples -------------------------------------------------------------------------------
console.log(translateToTitleCase("Into unmerciful the entreating stronger to of word guessing."));
console.log(translateToTitleCase("the OLD MAN aND THE sEa"));





I think my coding is still a bit "noisy" with the usage of all those brackets, chained methods and concatenation.



Any ideas about how to improve my implementation?



Perhaps some cool new ES6-feature I wasn't aware of.



What would you have done differently and why?










share|improve this question











$endgroup$




The task is to write a JavaScript-function which translates a given blank-separated sentence to title-case.



Means that all words shall start with a capital and then the rest of the word in lower-case. But: A certain, specified set of conjunctions, preposition as well as article shall be all lower-case.



Example: "The second of the four items." becomes "The Second of the Four Items.".



Here's my implementation of such a function:






function translateToTitleCase(str) 
const translateWord = (sWord) =>
return sWord.slice(0, 1).toUpperCase() + sWord.slice(1).toLowerCase();


const words = str.split(" ");

words[0] = translateWord(words[0]);

for (let i = 1; i < words.length; i++)
if (!["of", "and", "the", "to"].includes(words[i].toLowerCase()))
words[i] = translateWord(words[i]);
else
words[i] = words[i].toLowerCase(); // Make sure is's the correct case, when the sentence (or parts of it) is given in uppercase.



return words.join(" ");


// -- Examples -------------------------------------------------------------------------------
console.log(translateToTitleCase("Into unmerciful the entreating stronger to of word guessing."));
console.log(translateToTitleCase("the OLD MAN aND THE sEa"));





I think my coding is still a bit "noisy" with the usage of all those brackets, chained methods and concatenation.



Any ideas about how to improve my implementation?



Perhaps some cool new ES6-feature I wasn't aware of.



What would you have done differently and why?






function translateToTitleCase(str) 
const translateWord = (sWord) =>
return sWord.slice(0, 1).toUpperCase() + sWord.slice(1).toLowerCase();


const words = str.split(" ");

words[0] = translateWord(words[0]);

for (let i = 1; i < words.length; i++)
if (!["of", "and", "the", "to"].includes(words[i].toLowerCase()))
words[i] = translateWord(words[i]);
else
words[i] = words[i].toLowerCase(); // Make sure is's the correct case, when the sentence (or parts of it) is given in uppercase.



return words.join(" ");


// -- Examples -------------------------------------------------------------------------------
console.log(translateToTitleCase("Into unmerciful the entreating stronger to of word guessing."));
console.log(translateToTitleCase("the OLD MAN aND THE sEa"));





function translateToTitleCase(str) 
const translateWord = (sWord) =>
return sWord.slice(0, 1).toUpperCase() + sWord.slice(1).toLowerCase();


const words = str.split(" ");

words[0] = translateWord(words[0]);

for (let i = 1; i < words.length; i++)
if (!["of", "and", "the", "to"].includes(words[i].toLowerCase()))
words[i] = translateWord(words[i]);
else
words[i] = words[i].toLowerCase(); // Make sure is's the correct case, when the sentence (or parts of it) is given in uppercase.



return words.join(" ");


// -- Examples -------------------------------------------------------------------------------
console.log(translateToTitleCase("Into unmerciful the entreating stronger to of word guessing."));
console.log(translateToTitleCase("the OLD MAN aND THE sEa"));






javascript strings






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 6 hours ago







michael.zech

















asked 6 hours ago









michael.zechmichael.zech

1,7631735




1,7631735











  • $begingroup$
    I'd argue that the functionality should be changed slightly – this'll trip over words like xkcd and eBay – but I suppose that's not really in-scope for Code Review.
    $endgroup$
    – wizzwizz4
    44 mins ago

















  • $begingroup$
    I'd argue that the functionality should be changed slightly – this'll trip over words like xkcd and eBay – but I suppose that's not really in-scope for Code Review.
    $endgroup$
    – wizzwizz4
    44 mins ago
















$begingroup$
I'd argue that the functionality should be changed slightly – this'll trip over words like xkcd and eBay – but I suppose that's not really in-scope for Code Review.
$endgroup$
– wizzwizz4
44 mins ago





$begingroup$
I'd argue that the functionality should be changed slightly – this'll trip over words like xkcd and eBay – but I suppose that's not really in-scope for Code Review.
$endgroup$
– wizzwizz4
44 mins ago











1 Answer
1






active

oldest

votes


















5












$begingroup$

I find this code quite reasonable on the whole, but you might consider the following suggestions relating to consistency, succinctness and semantics.




Move and rename the inner helper function



translateWord is reusable as a general utility function and seems better-placed in the global scope and renamed to titleCase. This meshes with similarly-named Ruby, Python and PHP builtins (titlecase, title, ucfirst, respectively). When I see "translate", I think of linguistics or mathematics before I think of strings or casing.



Excessive calls to toLowerCase



.toLowerCase() is more efficient called once on the entire sentence before splitting rather than incurring the overhead of calling it multiple times per word. With this in mind, you can skip calling the titleCase function described above if you wish.



Improve "ignore" list



if (!["of", "and", "the", "to"].includes(words[i].toLowerCase())) {


is problematic for a few reasons:



  • It creates a new array object for every word. Move initialization to the top of the function and create it once.


  • Hardcoding restricts your function's reusability. Making this ignore list a default parameter allows the client to adjust the list as needed.

  • Giving this array a variable name makes its purpose more obvious.

  • Although the array is small, it needs to be traversed linearly to perform a lookup; using a set improves semantics, readability and time complexity all at once and is the ideal structure for testing membership.

Avoid the loop



This task is a map operation: each word has a function applied to it. You can roll split, map (your for loop) and join into one call to replace, which takes a regular expression that splits on non-word characters and applies the titleCase function to each one that passes the ignore test.



Minor points




  • sWord.slice(0, 1) can be sWord[0].


  • sWord is an okay variable name, but str (matching your outer function) or word seems more consistent.

  • Unless there is a good hoisting or context reason, I'd make the outer function also use an arrow function for consistency with your inner function.

A rewrite






const titleCaseWords = (words, ignore=["of", "and", "the", "to"]) => 
ignore = new Set(ignore);

return words.replace(/w+/g, (word, i) =>
word = word.toLowerCase();

if (i && ignore.has(word))
return word;


return word[0].toUpperCase() + word.slice(1);
);
;

[
"Into unmerciful the entreating stronger to of word guessing.",
"the OLD MAN aND THE sEa"
].forEach(test => console.log(titleCaseWords(test)));








share|improve this answer











$endgroup$













    Your Answer





    StackExchange.ifUsing("editor", function ()
    return StackExchange.using("mathjaxEditing", function ()
    StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
    StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
    );
    );
    , "mathjax-editing");

    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: "196"
    ;
    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
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f217006%2fa-function-which-translates-a-sentence-to-title-case%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









    5












    $begingroup$

    I find this code quite reasonable on the whole, but you might consider the following suggestions relating to consistency, succinctness and semantics.




    Move and rename the inner helper function



    translateWord is reusable as a general utility function and seems better-placed in the global scope and renamed to titleCase. This meshes with similarly-named Ruby, Python and PHP builtins (titlecase, title, ucfirst, respectively). When I see "translate", I think of linguistics or mathematics before I think of strings or casing.



    Excessive calls to toLowerCase



    .toLowerCase() is more efficient called once on the entire sentence before splitting rather than incurring the overhead of calling it multiple times per word. With this in mind, you can skip calling the titleCase function described above if you wish.



    Improve "ignore" list



    if (!["of", "and", "the", "to"].includes(words[i].toLowerCase())) {


    is problematic for a few reasons:



    • It creates a new array object for every word. Move initialization to the top of the function and create it once.


    • Hardcoding restricts your function's reusability. Making this ignore list a default parameter allows the client to adjust the list as needed.

    • Giving this array a variable name makes its purpose more obvious.

    • Although the array is small, it needs to be traversed linearly to perform a lookup; using a set improves semantics, readability and time complexity all at once and is the ideal structure for testing membership.

    Avoid the loop



    This task is a map operation: each word has a function applied to it. You can roll split, map (your for loop) and join into one call to replace, which takes a regular expression that splits on non-word characters and applies the titleCase function to each one that passes the ignore test.



    Minor points




    • sWord.slice(0, 1) can be sWord[0].


    • sWord is an okay variable name, but str (matching your outer function) or word seems more consistent.

    • Unless there is a good hoisting or context reason, I'd make the outer function also use an arrow function for consistency with your inner function.

    A rewrite






    const titleCaseWords = (words, ignore=["of", "and", "the", "to"]) => 
    ignore = new Set(ignore);

    return words.replace(/w+/g, (word, i) =>
    word = word.toLowerCase();

    if (i && ignore.has(word))
    return word;


    return word[0].toUpperCase() + word.slice(1);
    );
    ;

    [
    "Into unmerciful the entreating stronger to of word guessing.",
    "the OLD MAN aND THE sEa"
    ].forEach(test => console.log(titleCaseWords(test)));








    share|improve this answer











    $endgroup$

















      5












      $begingroup$

      I find this code quite reasonable on the whole, but you might consider the following suggestions relating to consistency, succinctness and semantics.




      Move and rename the inner helper function



      translateWord is reusable as a general utility function and seems better-placed in the global scope and renamed to titleCase. This meshes with similarly-named Ruby, Python and PHP builtins (titlecase, title, ucfirst, respectively). When I see "translate", I think of linguistics or mathematics before I think of strings or casing.



      Excessive calls to toLowerCase



      .toLowerCase() is more efficient called once on the entire sentence before splitting rather than incurring the overhead of calling it multiple times per word. With this in mind, you can skip calling the titleCase function described above if you wish.



      Improve "ignore" list



      if (!["of", "and", "the", "to"].includes(words[i].toLowerCase())) {


      is problematic for a few reasons:



      • It creates a new array object for every word. Move initialization to the top of the function and create it once.


      • Hardcoding restricts your function's reusability. Making this ignore list a default parameter allows the client to adjust the list as needed.

      • Giving this array a variable name makes its purpose more obvious.

      • Although the array is small, it needs to be traversed linearly to perform a lookup; using a set improves semantics, readability and time complexity all at once and is the ideal structure for testing membership.

      Avoid the loop



      This task is a map operation: each word has a function applied to it. You can roll split, map (your for loop) and join into one call to replace, which takes a regular expression that splits on non-word characters and applies the titleCase function to each one that passes the ignore test.



      Minor points




      • sWord.slice(0, 1) can be sWord[0].


      • sWord is an okay variable name, but str (matching your outer function) or word seems more consistent.

      • Unless there is a good hoisting or context reason, I'd make the outer function also use an arrow function for consistency with your inner function.

      A rewrite






      const titleCaseWords = (words, ignore=["of", "and", "the", "to"]) => 
      ignore = new Set(ignore);

      return words.replace(/w+/g, (word, i) =>
      word = word.toLowerCase();

      if (i && ignore.has(word))
      return word;


      return word[0].toUpperCase() + word.slice(1);
      );
      ;

      [
      "Into unmerciful the entreating stronger to of word guessing.",
      "the OLD MAN aND THE sEa"
      ].forEach(test => console.log(titleCaseWords(test)));








      share|improve this answer











      $endgroup$















        5












        5








        5





        $begingroup$

        I find this code quite reasonable on the whole, but you might consider the following suggestions relating to consistency, succinctness and semantics.




        Move and rename the inner helper function



        translateWord is reusable as a general utility function and seems better-placed in the global scope and renamed to titleCase. This meshes with similarly-named Ruby, Python and PHP builtins (titlecase, title, ucfirst, respectively). When I see "translate", I think of linguistics or mathematics before I think of strings or casing.



        Excessive calls to toLowerCase



        .toLowerCase() is more efficient called once on the entire sentence before splitting rather than incurring the overhead of calling it multiple times per word. With this in mind, you can skip calling the titleCase function described above if you wish.



        Improve "ignore" list



        if (!["of", "and", "the", "to"].includes(words[i].toLowerCase())) {


        is problematic for a few reasons:



        • It creates a new array object for every word. Move initialization to the top of the function and create it once.


        • Hardcoding restricts your function's reusability. Making this ignore list a default parameter allows the client to adjust the list as needed.

        • Giving this array a variable name makes its purpose more obvious.

        • Although the array is small, it needs to be traversed linearly to perform a lookup; using a set improves semantics, readability and time complexity all at once and is the ideal structure for testing membership.

        Avoid the loop



        This task is a map operation: each word has a function applied to it. You can roll split, map (your for loop) and join into one call to replace, which takes a regular expression that splits on non-word characters and applies the titleCase function to each one that passes the ignore test.



        Minor points




        • sWord.slice(0, 1) can be sWord[0].


        • sWord is an okay variable name, but str (matching your outer function) or word seems more consistent.

        • Unless there is a good hoisting or context reason, I'd make the outer function also use an arrow function for consistency with your inner function.

        A rewrite






        const titleCaseWords = (words, ignore=["of", "and", "the", "to"]) => 
        ignore = new Set(ignore);

        return words.replace(/w+/g, (word, i) =>
        word = word.toLowerCase();

        if (i && ignore.has(word))
        return word;


        return word[0].toUpperCase() + word.slice(1);
        );
        ;

        [
        "Into unmerciful the entreating stronger to of word guessing.",
        "the OLD MAN aND THE sEa"
        ].forEach(test => console.log(titleCaseWords(test)));








        share|improve this answer











        $endgroup$



        I find this code quite reasonable on the whole, but you might consider the following suggestions relating to consistency, succinctness and semantics.




        Move and rename the inner helper function



        translateWord is reusable as a general utility function and seems better-placed in the global scope and renamed to titleCase. This meshes with similarly-named Ruby, Python and PHP builtins (titlecase, title, ucfirst, respectively). When I see "translate", I think of linguistics or mathematics before I think of strings or casing.



        Excessive calls to toLowerCase



        .toLowerCase() is more efficient called once on the entire sentence before splitting rather than incurring the overhead of calling it multiple times per word. With this in mind, you can skip calling the titleCase function described above if you wish.



        Improve "ignore" list



        if (!["of", "and", "the", "to"].includes(words[i].toLowerCase())) {


        is problematic for a few reasons:



        • It creates a new array object for every word. Move initialization to the top of the function and create it once.


        • Hardcoding restricts your function's reusability. Making this ignore list a default parameter allows the client to adjust the list as needed.

        • Giving this array a variable name makes its purpose more obvious.

        • Although the array is small, it needs to be traversed linearly to perform a lookup; using a set improves semantics, readability and time complexity all at once and is the ideal structure for testing membership.

        Avoid the loop



        This task is a map operation: each word has a function applied to it. You can roll split, map (your for loop) and join into one call to replace, which takes a regular expression that splits on non-word characters and applies the titleCase function to each one that passes the ignore test.



        Minor points




        • sWord.slice(0, 1) can be sWord[0].


        • sWord is an okay variable name, but str (matching your outer function) or word seems more consistent.

        • Unless there is a good hoisting or context reason, I'd make the outer function also use an arrow function for consistency with your inner function.

        A rewrite






        const titleCaseWords = (words, ignore=["of", "and", "the", "to"]) => 
        ignore = new Set(ignore);

        return words.replace(/w+/g, (word, i) =>
        word = word.toLowerCase();

        if (i && ignore.has(word))
        return word;


        return word[0].toUpperCase() + word.slice(1);
        );
        ;

        [
        "Into unmerciful the entreating stronger to of word guessing.",
        "the OLD MAN aND THE sEa"
        ].forEach(test => console.log(titleCaseWords(test)));








        const titleCaseWords = (words, ignore=["of", "and", "the", "to"]) => 
        ignore = new Set(ignore);

        return words.replace(/w+/g, (word, i) =>
        word = word.toLowerCase();

        if (i && ignore.has(word))
        return word;


        return word[0].toUpperCase() + word.slice(1);
        );
        ;

        [
        "Into unmerciful the entreating stronger to of word guessing.",
        "the OLD MAN aND THE sEa"
        ].forEach(test => console.log(titleCaseWords(test)));





        const titleCaseWords = (words, ignore=["of", "and", "the", "to"]) => 
        ignore = new Set(ignore);

        return words.replace(/w+/g, (word, i) =>
        word = word.toLowerCase();

        if (i && ignore.has(word))
        return word;


        return word[0].toUpperCase() + word.slice(1);
        );
        ;

        [
        "Into unmerciful the entreating stronger to of word guessing.",
        "the OLD MAN aND THE sEa"
        ].forEach(test => console.log(titleCaseWords(test)));






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 2 hours ago

























        answered 2 hours ago









        ggorlenggorlen

        576213




        576213



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Code Review 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.

            Use MathJax to format equations. MathJax reference.


            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%2fcodereview.stackexchange.com%2fquestions%2f217006%2fa-function-which-translates-a-sentence-to-title-case%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

            Jet Time Laivasto | Lähteet | Aiheesta muualla | NavigointivalikkoJet Time - The CompanyThe CompanyManagementJet Time aloittaa lauantaina Suomi-rekisterissä olevalla Boeing 737 -koneellaJettime Finland Fleet Details and HistoryJettime Fleet Details and HistoryRegional Jet OÜ takes over ATR production for SASJet Time Returns To Its Core BusinessYhtiön kotisivutlaajentamalla

            Olympian arkeologinen museo Sisällysluettelo Historia ja rakennus | Kokoelmat | Lähteet | Aiheesta muualla | Navigointivalikko37°38′36″N, 21°37′46″EInfobox OKArchaeological Museum of Olympia: HistoryArchaeological Museum of Olympia: DescriptionΜουσείο Ιστορίας των Ολυμπιακών Αγώνων της Αρχαιότητας: ΙστορικόArchaeological Museum of Olympia

            Äpy Sisällysluettelo Äpyt kautta historian | Esimerkkejä Äpy-huumorista | Katso myös | Kirjallisuutta | Aiheesta muualla | Navigointivalikkowww.äpy.fi