return""+code+": Found a closing bracket, '"+translit+"', without a matching open bracket. Perhaps a [#COMMENT] incorrectly written as [COMMENT], or a [*CORRECTION] written incorrectly as [CORRECTION], caused this.";
return""+code+": Found an illegal open bracket (in context, this is '"+translit+"'). Perhaps there is a [#COMMENT] written incorrectly as [COMMENT], or a [*CORRECTION] written incorrectly as [CORRECTION], or an unmatched open bracket?";
return""+code+": Found an illegal at sign, @ (in context, this is "+translit+"). This folio marker has a period, '.', at the end of it, which is illegal.";
return""+code+": The "+traits.shortTranslitName()+" {?}, found alone, may intend U+0F08, but it may intend a question mark, i.e. '?', in the output. It may even mean that the original text could not be deciphered with certainty, like the "+traits.shortTranslitName()+" {[?]} does.";
return""+code+": Found a backslash, \\, which the ACIP Tibetan Input Code standard says represents a Sanskrit virama. In practice, though, this is so often misused (to represent U+0F3D) that {\\} always generates this error. If you want a Sanskrit virama, change the input document to use {\\u0F84} instead of {\\}. If you want U+0F3D, use {/NYA/} or {/NYA\\u0F3D}.";
case116:
ThdlDebug.verify(translit.length()==1);
return""+code+": Found an illegal character, '"+translit+"', with ordinal (in decimal) "+(int)translit.charAt(0)+".";
return""+code+": Cannot convert ACIP {"+translit+"} because we would be required to assume that {A} is a consonant, when it is not clear if it is a consonant or a vowel.";
return""+code+": Cannot convert "+traits.shortTranslitName()+" {"+translit+"} because it ends with a disambiguator (i.e., '"+traits.disambiguator()+"').";
return""+code+": Cannot convert the "+traits.shortTranslitName()+" {"+translit+"} to Tibetan because it is unclear what the result should be. The correct output would likely require special mark-up.";
return""+code+": The tsheg bar (\"syllable\") {"+translit+"} has no legal parses.";
case135:
ThdlDebug.verify(translit.length()==1);
return""+code+": The Unicode escape '"+translit+"' with ordinal (in decimal) "+(int)translit.charAt(0)+" is specified by the Extended Wylie Transliteration Scheme (EWTS), but is in the private-use area (PUA) of Unicode and will thus not be written out into the output lest you think other tools will be able to understand this non-standard construction.";
case136:
ThdlDebug.verify(translit.length()==1);
return""+code+": The Unicode escape with ordinal (in decimal) "+(int)translit.charAt(0)+" does not match up with any TibetanMachineWeb glyph.";
// See 137 below.
case138:
ThdlDebug.verify(translit.length()==1);
return""+code+": The Unicode escape '"+translit+"' with ordinal (in decimal) "+(int)translit.charAt(0)+" is in the Tibetan range of Unicode (i.e., [U+0F00, U+0FFF]), but is a reserved code in that area.";
return""+code+": While waiting for a closing bracket, an opening bracket, '"+translit+"', was found instead. Nesting of bracketed expressions is not permitted.";
return""+code+": Because you requested conversion to a Unicode text file, there is no way to indicate that the font size is supposed to decrease starting here and continuing until error 143. That is, this is the beginning of a region in YIG CHUNG.";
return""+code+": Because you requested conversion to a Unicode text file, there is no way to indicate that the font size is supposed to increase (go back to the size it was before the last error 142, that is) starting here. That is, this is the end of a region in YIG CHUNG.";
thrownewError("Nah -- we handle this one in the code because the message is complicated for 501");
case502:
return""+code+": The last stack does not have a vowel in {"+translit+"}; this may indicate a typo, because Sanskrit, which this probably is (because it's not legal Tibetan), should have a vowel after each stack.";
return""+code+": Though {"+translit+"} is unambiguous, it would be more computer-friendly if '+' signs were used to stack things because there are two (or more) ways to interpret this ACIP if you're not careful.";
return""+code+": The ACIP {"+translit+"} is treated by this converter as U+0F35, but sometimes might represent U+0F14 in practice. To avoid seeing this warning again, change the input to use {\\u0F35} instead of {"+translit+"}.";
case505:
return""+code+": There is a useless disambiguator in {"+translit+"}.";
return""+code+": There is a stack of three or more consonants in {"+translit+"} that uses at least one '+' but does not use a '+' between each consonant.";
return""+code+": There is a chance that the ACIP {"+translit+"} was intended to represent more consonants than we parsed it as representing -- GHNYA, e.g., means GH+NYA, but you can imagine seeing GH+N+YA and typing GHNYA for it too.";// TMW has glyphs for both GH+N+YA (G+H+N+YA) and GH+NYA (G+H+NYA).
return""+code+": The "+traits.shortTranslitName()+" {"+translit+"} has been interpreted as two stacks, not one, but you may wish to confirm that the original text had two stacks as it would be an easy mistake to make to see one stack (because there is such a stack used in Sanskrit transliteration for this particular sequence) and forget to input it with '+' characters.";
return""+code+": The "+traits.shortTranslitName()+" {"+translit+"} has an initial sequence that has been interpreted as two stacks, a prefix and a root stack, not one nonnative stack, but you may wish to confirm that the original text had two stacks as it would be an easy mistake to make to see one stack (because there is such a stack used in Sanskrit transliteration for this particular sequence) and forget to input it with '+' characters.";
return""+code+": The "+traits.shortTranslitName()+" {"+translit+"} cannot be represented with the TibetanMachine or TibetanMachineWeb fonts because no such glyph exists in these fonts. The TibetanMachineWeb font has only a limited number of ready-made, precomposed glyphs, and {"+translit+"} is not one of them.";
return""+code+": There is a chance that the ACIP {"+translit+"} was intended to represent more consonants than we parsed it as representing -- GHNYA, e.g., means GH+NYA, but you can imagine seeing GH+N+YA and typing GHNYA for it too. In fact, there are glyphs in the Tibetan Machine font for N+N+Y, N+G+H, G+N+Y, G+H+N+Y, T+N+Y, T+S+TH, T+S+N, T+S+N+Y, TS+NY, TS+N+Y, H+N+Y, M+N+Y, T+S+M, T+S+M+Y, T+S+Y, T+S+R, T+S+V, N+T+S, T+S, S+H, R+T+S, R+T+S+N, R+T+S+N+Y, and N+Y, indicating the importance of these easily mistyped stacks, so the possibility is very real.";
out.println("ACIP->Tibetan WARNINGS are as follows, and appear in their short forms, embedded");
out.println("in the output, like [#WARNING 510: {X}]:");
out.println("");
for(intnum=MIN_WARNING;num<=MAX_WARNING;num++){
if(501==num){
out.println("501: Using "+translit+", but only because the tool's knowledge of prefix rules (see the documentation) says that "+"XX"+" is not a legal Tibetan tsheg bar (\"syllable\")");
