Node.js Translation to Spanish - ( 1118 words) (Part-76)

in #utopian-io • 5 years ago

Repository

https://github.com/nodejs/i18n

Project Details

Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser.

Node.js came into existence when the original developers of JavaScript extended it from something you could only run in the browser to something you could run on your machine as a standalone application.

In simple words, it's an open source execution environment for developing web applications, which is event-based, it uses the V8 engine to provide an execution environment that compiles and executes JavaScript at a higher speed. It is possible to run Node.js without any restriction on Windows, Linux and Mac OS X.

It should be noted that it is NOT a server language, this means that it executes code, so it could be understood as an interpreter.

Contribution Specifications

Node.js is currently being translated into 33 languages. I'm contributing to translate it into the Spanish language.

image.png

So far, we have managed to translate 74% of the project!

Translation Overview

For this occasion I translated the folder Perf_hooks.md. The Performance Timing API, allows developers to take precise measurements of the effects of userland code in the event loop and how that affects the performance of your application.

Basically, if you want to measure the performance of your app in a serious manner, you’ll want to read about perf_hooks at some point.

To put it simply, with this module you can perform actions at different stages of the life of a callback function.

As an example of the work done, I will use part of the section Class: Performance:

English:

performance.measure(name, startMark, endMark)

Creates a new PerformanceMeasure entry in the Performance Timeline. A PerformanceMeasure is a subclass of PerformanceEntry whose performanceEntry.entryType is always measure, and whose performanceEntry.duration measures the number of milliseconds elapsed since startMark and endMark.

The startMark argument may identify any existing PerformanceMark in the Performance Timeline, or may identify any of the timestamp properties provided by the PerformanceNodeTiming class. If the named startMark does not exist, then startMark is set to [timeOrigin][] by default.

The endMark argument must identify any existing PerformanceMark in the Performance Timeline or any of the timestamp properties provided by the PerformanceNodeTiming class. If the named endMark does not exist, an error will be thrown.
performance.node

Spanish:

performance.measure(name, startMark, endMark)

Crea una nueva entrada PerformanceMeasure en la Línea de Tiempo de Rendimiento. Una PerformanceMeasure es una subclase de PerformanceEntry cuyo performanceEntry.entryType es siempre measure, y cuya performanceEntry.duration mide el número de milisegundos transcurridos desde startMark y endMark.

El argumento startMark puede identificar cualquier PerformanceMark existente en la Línea de Tiempo de Rendimiento, o puede identificar cualquiera de las propiedades timestamp proporcionadas por la clase PerformanceNodeTiming. Si el nombre startMark no existe, entonces startMark es establecido como [timeOrigin][] por defecto.

El argumento endMark debe especificar cualquier PerformanceMark existente en la Línea de Tiempo de Rendimiento o cualquiera de las propiedades timestamp proporcionadas por la clase PerformanceNodeTiming. Si el endMark nombrado no existe, se producirá un error.

Languages

This contribution was translated from English to Spanish.

Word Count

The number of words reflected in the title doesn't include words that didn't require a translation.

  • In this contribution, I've translated 1118 words.
  • I've translated a total of 104211 words so far*

*Considering non-translatable content (proper names, functions, codes, etc.)

To see my previous contributions in this project, check this!

Check.gif

Part 76

Part 74

Part 73

Part 72

Part 71

Part 70

From Part 62 to Part 69

Part 61

Parts 59 and 60

Parts 57 and 58

Part 56

Parts 54 and 55

Part 53

Part 52

From Part 41 to Part 51

From Part 14 to Part 40

Part 13

Parts 11 and 12.

From Part 7 to Part 10

From Part 1 to Part 6

Proof of Authorship

image.png

This counter includes non-translatable words, so it is necessary to work on more content to extract an average of 1000 translatable words.

You can check My Crowdin Profile for verify my contribution in this project.c

#translations #davinci #node-js
5 years ago in #utopian-io by
$12.40
68 votes
Reply 3
Sort:  
  • Trending
    • [-]
     5 years ago  

    Greetings, @cremisi. Thanks for submitting your contribution!

    • The presentation and contents of your post satisfy the requirements for a complete evaluation of your contribution.
    • The translated content fits coherently the general meaning and use of the addressed strings.
    • Thanks for adding an example of your work on the project. However, we invite you to be a little more explicative in your upcoming reports.
    • You did a very precise use of the terminology and technical language involved in this translation.

    Congratulations on this collaboration!

    Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

    To view those questions and the relevant answers related to your post, click here.

    Chat with us on Discord

    [-]
     5 years ago  

    Thank you for your review, @alejohannes! Keep up the good work!

    $0.00
      Reply
      [-]
       5 years ago  

      Hey, @cremisi!

      Thanks for contributing on Utopian.
      We’re already looking forward to your next contribution!

      Get higher incentives and support Utopian.io!
      Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).

      Want to chat? Join us on Discord https://discord.gg/h52nFrV.

      Vote for Utopian Witness!

      $0.00
        Reply