{"trustable":true,"prependHtml":"\u003cscript\u003e window.katexOptions \u003d { disable: true }; \u003c/script\u003e\n\u003cscript type\u003d\"text/x-mathjax-config\"\u003e\n MathJax.Hub.Config({\n tex2jax: {\n inlineMath: [[\u0027$$$\u0027,\u0027$$$\u0027], [\u0027$\u0027,\u0027$\u0027]],\n displayMath: [[\u0027$$$$$$\u0027,\u0027$$$$$$\u0027], [\u0027$$\u0027,\u0027$$\u0027]]\n }\n });\n\u003c/script\u003e\n\u003cscript async src\u003d\"https://mathjax.codeforces.org/MathJax.js?config\u003dTeX-AMS-MML_HTMLorMML\" type\u003d\"text/javascript\"\u003e\u003c/script\u003e","sections":[{"title":"","value":{"format":"HTML","content":"\u003cdiv class\u003d\"panel_content\"\u003e As an Android developer, itˇs really not easy to figure out a newer version of two kernels, because Android is updated so frequently and has many branches. Fortunately, Google identifies individual builds with a short build code, e.g. FRF85B.\u003cbr\u003e\u003cbr\u003e The first letter is the code name of the release family, e.g. F is Froyo. The code names are ordered alphabetically. The latest code name is K (KitKat).\u003cbr\u003eThe second letter is a branch code that allows Google to identify the exact code branch that the build was made from, and R is by convention the primary release branch.\u003cbr\u003e\u003cbr\u003e The next letter and two digits are a date code. The letter counts quarters, with A being Q1 2009. Therefore, F is Q2 2010. The two digits count days within the quarter, so F85 is June 24 2010.\u003cbr\u003e\u003cbr\u003e Finally, the last letter identifies individual versions related to the same date code, sequentially starting with A; A is actually implicit and usually omitted for brevity.\u003cbr\u003e\u003cbr\u003e Please develop a program to compare two Android build numbers.\u003c/div\u003e"}},{"title":"Input","value":{"format":"HTML","content":" The first line is an integer n (1 \u0026lt;\u003d n \u0026lt;\u003d 2000), which indicates how many test cases need to process.\u003cbr\u003e\u003cbr\u003e Each test case consists of a single line containing two build numbers, separated by a space character. "}},{"title":"Output","value":{"format":"HTML","content":" For each test case, output a single line starting with ¨Case #: 〃 (# means the number of the test case). Then, output the result of release comparison as follows:\u003cbr\u003e\u003cbr\u003e ● Print \"\u0026lt;\" if the release of the first build number is lower than the second one;\u003cbr\u003e ● Print \"\u003d\" if the release of the first build number is same as he second one;\u003cbr\u003e ● Print \"\u0026gt;\" if the release of the first build number is higher than the second one.\u003cbr\u003e\u003cbr\u003e Continue to output the result of date comparison as follows:\u003cbr\u003e ● Print \"\u0026lt;\" if the date of the first build number is lower than the second one;\u003cbr\u003e ● Print \"\u003d\" if the date of the first build number is same as he second one;\u003cbr\u003e ● Print \"\u0026gt;\" if the date of the first build number is higher than the second one.\u003cbr\u003e\u003cbr\u003e If two builds are not in the same code branch, just compare the date code; if they are in the same code branch, compare the date code together with the individual version."}},{"title":"Sample","value":{"format":"HTML","content":"\u003ctable class\u003d\u0027vjudge_sample\u0027\u003e\n\u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eInput\u003c/th\u003e\n \u003cth\u003eOutput\u003c/th\u003e\n \u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cpre\u003e2\r\nFRF85B EPF21B\r\nKTU84L KTU84M\u003c/pre\u003e\u003c/td\u003e\n \u003ctd\u003e\u003cpre\u003eCase 1: \u0026gt; \u0026gt;\r\nCase 2: \u003d \u0026lt;\u003c/pre\u003e\u003c/td\u003e\n \u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n"}}]}