https://trac.webkit.org/changeset/214244/webkit seems to have introduced compilation errors on such platforms other than USE(CF) || USE(GLIB). There're some code like String::fromUTF8("Look Up “<selection>”", "Look Up context menu item with selected word") but String::fromUTF8() cannot take two strings (for string and description).
Created attachment 311680 [details] Patch
Created attachment 311684 [details] Patch
Would it be better/clearer to just remove the second argument instead, since WEB_UI_STRING degrades to String::fromUTF8 in this case anyway?
(In reply to Michael Catanzaro from comment #3) > Would it be better/clearer to just remove the second argument instead, since > WEB_UI_STRING degrades to String::fromUTF8 in this case anyway? The original patch just commented it out. I thought it would be more consistent with the rest of the file's contents to use WEB_UI_STRING.
Comment on attachment 311684 [details] Patch Clearing flags on attachment: 311684 Committed r217686: <http://trac.webkit.org/changeset/217686>
All reviewed patches have been landed. Closing bug.