View source for Thread:Support/Request to add project: Blockly

CLOSED This issue is closed by Espertus

I cannot see any things to translate..... :(

The message group has not yet been fully vetted. Some strings are empty and should be ignored or optional. I'm working on it.

CLOSED This issue is closed by Espertus

Needs proper plural support. Not all languages only have singular and plural.

Are there existing JavaScript functions for handing PLURAL in the various languages?

There's jQuery.i18n at https://github.com/Wikimedia/jquery.i18n which has it. You could use the parsers and the format, or adopt the framework.

Our TL has rejected jQuery, and I don't think we'll get to a workaround. :-(

CLOSED This issue is closed

Documentation and message text do not relate to each other.

This no longer appears to be an active string.

CLOSED This issue is closed by siebrand

This message must be fuzzyed except English, Korean, Japanese, Malay, Ukrainian, and qqq.

File:Yes check.svg Done

CLOSED This issue is closed

"Error parsing XML: (error msg) Abandon changes?"

According to the documentation, the user gets the buttons "OK" and "Cancel" to choose from. This is unclear and incorrect, as choosing "OK" would actually cancel the changes, and choosing "Cancel" would keep the changes and return the user to the editor to fix it manually (which is the opposite of cancelling).

At minimum, the buttons presented should be "Yes" and "No". Much better still would be "Abandon" and "Keep".

This is an excellent point, which I will bring up with my tech lead.

I spoke to my tech lead, and he said:

• You're right.
• The reason we have OK/Cancel is we're using the default dialog window.
• This message is not frequently seen.

For now, I will rephrase the English-language message to make it clearer what the user should do. It may take a few days for the change to show up in translatewiki.

Thank you.

CLOSED This issue is closed

Does 'repeat' need to be translated or left in English?

"Repeat" should be translated in the same manner as on the "repeat" block. See Blockly:Maze.repeatUntil/ms.

Thank you for the question and for helping translate Blockly.

CLOSED This issue is closed by Espertus

As documentation: this should only be changed by Blockly developers, not translators.

We have removed this entry.

CLOSED This issue is closed

"Pegman" should be "(The) player" for consistency with other messages.

• Maze.instructions5 ("Breaking a problem into two pieces can make things easier.")

You are absolutely right. I am not sure why I didn't seen your message until now. As you can see, we have removed references to Pegman from the messages.

CLOSED This issue is closed

The link in documentation does not work.

File:Yes check.svg Done. Fixed the documentation.

CLOSED This issue is closed by Purodha

Duplicate spaces (after full stops) in source messages:

• Core-2939986560796703529-XML ERROR ("Could not load your saved file. Perhaps it was created with a different version of Blockly?")
• Maze-3542684864087093156-Maze.instructions1 ("A program is a sequence of blocks. Stack a couple of 'move forward' blocks together to help me reach the goal.")
• Maze-4117834464422802314-Maze.instructions3 ("Computers have limited memory. Reach the end of this path using only two blocks. Use 'repeat' to run a block more than once.")
• Maze-7837544939813721855-Maze.instructions6 ("An 'if' block will do something only if the condition is true. Try turning left if there is a path to the left.")
• Maze-4572857545803877392-Maze.instructions10 ("Can you solve this complicated maze? Try following the left-hand wall. Advanced programmers only!")

Thank you. I grew up in the old days of typewriters. I've made the fix in the source files (although they won't show up on translatewiki immediately).

Actually, before I make this change, could you tell me why you think two spaces is incorrect? We're willing to make a change if that's site policy but not if it is personal preference.

(Sorry for not responding sooner. I only just learned how to see my support messages.)

CLOSED This issue is closed

I'm working on creating message documentation for Blockly. I'm not sure how to describe tooltip messages, as shown in yellow in the picture below. What would be good message documentation for "Return the square root of a number."?

Screenshots can be used, though a lot of work. At least do mention it is a tooltip.

Sure, screenshots are always nice, but I would consider something like “A tooltip for a ‘square root’ block explaining the block computes the square root of its input” quite sufficient.

CLOSED This issue is closed by siebrand

This message should possibly be ignored, at least for time being and if it is true that we have accidental translations. Of course, they may be not accidental at all. :-)

Yes. I am trying to figure out how to mark it optional.

@Espertus: It's explained at mw:Help:Extension:Translate/Group_configuration#TAGS.

I fixed it here.

CLOSED This issue is closed

String no longer in use.

Needs proper plural support. Not all languages only have singular and plural.

CLOSED This issue is closed by Espertus

Blockly likely does not have it, but here PLURAL or an equivlent should be used.

Blockly does not support plural.

CLOSED This issue is closed by siebrand

How should we translate the word block? Should we translate it as "city blocks"?

Blocks that children stack. See image.

Okay, thanks!

CLOSED This issue is closed by Espertus

These messages should be using something like PLURAL.

Yes, probably. We've been using a different (ad hoc) system and are just getting started with translatewiki.

CLOSED This issue is closed by Siebrand

• Translating:Blockly created
• Assorted checks to do
• Create coordination page/bug to discuss and work on XLIFF FFS

That looks like an awesome app. I've seen something like that in a TED talk recently. Can we do a hangout on this somewhere this weekend to see what we can make happen? Please contact me at siebrand AT wikimedia DOT org. I live in the Netherlands, so I'm UTC+1 (until Sunday, when that changes to UTC+2).

Status update for thread followers: Looks like we will be supporting this product within a few weeks.

Support was added!