docs: mi/doc-65/june-translations - #3972
Open
hajjimo wants to merge 2 commits into
Open
Conversation
June translations specific to Rafiki. Included in this batch Landing page Account Servicing Entity Clearing and Settlement Interledger Open Payments Payment Pointers Telemetry
✅ Deploy Preview for brilliant-pasca-3e80ec ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
the
pkg: documentation
Reapplied pnpm lint
🚀 Performance Test ResultsTest Configuration:
Test Metrics:
📜 Logs |
| variant: primary | ||
| attrs: | ||
| data-umami-event: Landing page - Rafiki docs | ||
| data-umami-event: Página de inicio - Documentos de Rafiki |
Contributor
There was a problem hiding this comment.
Note: Check w/ Sarah to see if this is all that's needed or if there's something to be done on her side
|
|
||
| <CardGrid> | ||
| <a class='card-link' href='/integration/playground/overview'> | ||
| <Card title='Try it out!' icon='document'> |
Contributor
There was a problem hiding this comment.
Did we get translations for the card titles?
| A response from an SPSP server means the URL is a payment pointer. | ||
| Si un servidor SPSP devuelve una respuesta, significa que la URL es un Payment Pointer. | ||
|
|
||
| ```http title="Example response" |
| You can determine whether a URL is a wallet address by sending a `GET` request to the URL with an `accept: application/json` header. | ||
| Puede determinar si una URL es una dirección de billetera enviando una solicitud `GET` a la URL con un encabezado `accept: application/json`. | ||
|
|
||
| ```http title="Example request" |
| A valid response means the URL is a wallet address. | ||
| Una respuesta válida significa que la URL es una dirección de billetera. | ||
|
|
||
| ```http title="Example response" |
| @@ -1,38 +1,48 @@ | |||
| --- | |||
| title: Pagos Abiertos | |||
Contributor
There was a problem hiding this comment.
The astro config still has the Spanish translation. I think it should be changed to Open Payments there, too.
| import { LinkOut } from '@interledger/docs-design-system' | ||
|
|
||
| Rafiki follows the <LinkOut href='https://openpayments.dev'>Open Payments</LinkOut> standard to enable third-party clients to securely retrieve account information and initiate payments from your customers’ accounts with their consent. The standard describes a uniform way to create and manage grants and resources for <LinkOut href='https://openpayments.dev/concepts/resources/#resource-types'>incoming payments, quotes, and outgoing payments</LinkOut>. | ||
| Rafiki sigue el estándar de <LinkOut href='https://openpayments.dev'>Open Payments</LinkOut> para permitir que los clientes externos recuperen de forma segura información de las cuentas y autoricen pagos desde las cuentas de sus clientes con su consentimiento. El estándar ofrece una forma uniforme de crear y gestionar concesiones y recursos para <LinkOut href='https://openpayments.dev/concepts/resources/#resource-types'>pagos entrantes, cotizaciones y pagos salientes</LinkOut>. |
Contributor
There was a problem hiding this comment.
Note to self. There are Spanish versions of Open Payments pages that this and other links could go to, but with the Open Payments doc restructure, there's a bit to catch up on. So let's wait on changing links here.
| ## Payment Pointers | ||
|
|
||
| A payment pointer is a standardized identifier for a payment account that supports Interledger payments. Each payment pointer must resolve to an HTTPS URL that serves as an [SPSP](/overview/concepts/interledger#simple-payment-setup-protocol-spsp) endpoint to facilitate sending and receiving ILP packets. | ||
| Un Payment Pointer es un identificador estandarizado para una cuenta de pago que admite pagos mediante Interledger. Cada Payment Pointer debe resolverse en una URL HTTPS que funcione como un punto final [SPSP](/es/overview/concepts/interledger#simple-payment-setup-protocol-spsp) para facilitar el envío y la recepción de paquetes ILP. |
Contributor
There was a problem hiding this comment.
This link isn't working quite right. The anchor/heading is probably not in English.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #Doc-65
Description of changes
June translations specific to Rafiki. Included in this batch
Landing page
Account Servicing Entity
Clearing and Settlement
Interledger
Open Payments
Payment Pointers
Telemetry
Checklist
docs:fixes #pnpm formatandpnpm lint