-
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GHAction - Commit content changes pulled from notion
- Loading branch information
1 parent
3286f49
commit d12c03a
Showing
39 changed files
with
413 additions
and
59 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,119 @@ | ||
--- | ||
title: Managing Large Projects- new books and adaptations | ||
sidebar_position: 1 | ||
slug: /adaptations | ||
--- | ||
|
||
|
||
|
||
A number of organizations have used Bloom to make a set of self-authored books and oversee the translation of these books into other languages. Most commonly, these organizations employ the following simple workflow: | ||
|
||
1. _New_ books are authored in a particular chosen majority language such as English, French, Russian, Hindi, etc. This collection of _original_ books constitutes a type of “parent” collection. | ||
2. The books in this “parent” collection are translated (and/or adapted) into various other local languages in various “daughter” collections. | ||
|
||
Chetana, for example, is an active user of Bloom. Most of their original titles first begin as an English publication. Following this, Chetana makes copies of these English books and adapts them into various other languages, such as Hindi and Tamil. | ||
|
||
|
||
Here is a sampling of [Chetana’s home page](https://bloomlibrary.org/chetana) on Bloom: | ||
|
||
|
||
![](./1271721441.png) | ||
|
||
|
||
In the following, we will present the steps for setting up the Bloom Collections for the Chetana project. | ||
|
||
|
||
# Make your “parent” collection visible to other collections {#4476b39998c04d9f8ec37fc1d98c0f7e} | ||
|
||
|
||
After your “parent” collection is established and you are ready to start making adaptations of those books into other languages, you need to make your parent collection visible to these other collections. | ||
|
||
1. **In the bottom left quadrant of Bloom, scroll to the bottom of the screen.** | ||
2. **Click on** **SHOW ANOTHER COLLECTION…** | ||
|
||
![](./1367602357.png) | ||
|
||
|
||
Bloom will open **Windows Explorer** to the Bloom folder. There you will find all of your Bloom collections. | ||
|
||
1. **Open the collection folder you want to become visible.** | ||
2. **Find the file ending with** **`.bloomCollection`** **and click on it.** | ||
3. **Click** **Open****.** | ||
|
||
![](./204384334.png) | ||
|
||
|
||
Your chosen “parent” collection will now appear in the bottom left quadrant under **Sources For New Books**. It will be listed after the section **Books From BloomLibrary.org**. | ||
|
||
|
||
# Make an adaptation of a book {#b0222b901f3c4af4ac57db65f9050812} | ||
|
||
|
||
To make an adaptation of one of your books: | ||
|
||
1. **In the bottom right quadrant, scroll down past Templates, past Sample Shells, and past any books in the Books From** [**BloomLibrary.org**](http://bloomlibrary.org/)**, until you see your parent collection and its books.** | ||
2. **Select the book.** | ||
3. **Click** **MAKE A BOOK USING THIS SOURCE**. | ||
|
||
![](./193378309.png) | ||
|
||
|
||
:::tip | ||
|
||
Warning: If you use Windows file explorer to create a copy of a Bloom book, that will lead to many problems; that copy will _not_ be a “Bloom-approved” copy of your original book. | ||
|
||
::: | ||
|
||
|
||
|
||
|
||
# Working with colleagues {#52fa9df6e98f42dd97b2b88c4e0114d2} | ||
|
||
|
||
There are two different workflows depending on whether or not you have reliable internet and a Bloom Enterprise subscription. Since Chetana has good internet and an Enterprise subscription, we’ll begin with that scenario. | ||
|
||
|
||
## Workflow 1: Organizations with reliable Internet _and_ an Enterprise subscription {#f32406d0e7af4191acf23a018a9810b0} | ||
|
||
|
||
Organizations with reliable internet and an Enterprise subscription will want to use Bloom’s powerful collaborative tool: [Team Collections](/team-collections-intro). | ||
|
||
|
||
Team Collections enables multiple people to collaborate together on Bloom books in a convenient, disciplined, and safe way using Dropbox’s cloud services. In a Team Collection, team members can “sign out” books. When they do so, they indicate to the rest of the team that they are working on the book, and while the book is signed out, other team members are prevented from accidentally editing that book, thus erasing their work. In this way, the Team Collection system allows books to be edited in a safe and disciplined way. | ||
|
||
|
||
Please refer to [Working with Team Collections](/working-with-team-collections) for further details. | ||
|
||
|
||
The above is the typical workflow for organizations with reliable internet and an Enterprise subscription. Additional guidance will be needed if your books are going to be subdivided according to reading level. | ||
|
||
|
||
## Workflow 2: Organizations with unreliable internet, or organizations with no Enterprise status {#c80ed9e840f246569ffea4cf5d5269ba} | ||
|
||
|
||
If the internet is unreliable for your team, Bloom’s Team Collections will not be a viable option. In this case, the project coordinator will need to carefully manage by various other means (USB keys, external hard drives, zip files, etc.) the creation, checking, revision, and publishing of new book titles. | ||
|
||
|
||
Once a collection of original titles are ready to be translated, Bloom does offer a means to bundle those files together in a package. | ||
|
||
|
||
Click the arrow beside your collection name: | ||
|
||
|
||
![](./1662008181.png) | ||
|
||
|
||
And then choose **Make Bloom Pack of Shell Books…** | ||
|
||
|
||
![](./1575640529.png) | ||
|
||
|
||
Distribute the `.BloomPack` file to your colleagues to copy to their computer. They should then click on that file. Bloom will then install that Source collection on their computer. | ||
|
||
|
||
![](./877570578.png) | ||
|
||
|
||
Once installed, that collection will appear in the Source For New Shells section, and they can begin the translation process. | ||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
--- | ||
title: Measuring the Impact of your Bloom Reader Campaigns with | ||
Distribution Tags | ||
sidebar_position: 5 | ||
slug: /br-campaigns | ||
--- | ||
|
||
|
||
|
||
Please refer to the following: | ||
|
||
|
||
[How to Collect Bloom Reader Analytics by Device](/how-to-collect-bloom-reader-analytics) | ||
|
||
|
||
[Measuring Your Reach with Bloom Analytics](/br-analytics) | ||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
--- | ||
title: Making a Translation “Snappy” | ||
sidebar_position: 4 | ||
slug: /snappy | ||
--- | ||
|
||
|
||
|
||
**by Kristine M. Trammell** | ||
|
||
|
||
I've heard literacy specialists denounce the translation of stories and other texts from one language to another and state rather proudly that they only promote original, creative writing. While it is essential to promote first language authors and create authentic cultural literature, many good reasons exist to translate other materials, such as multiplying the quantity of literature available in minority languages. | ||
|
||
|
||
Of course, there are also valid concerns about translating text from one language and culture to another. A translated text can be more challenging to read than prose written naturally. Without care, translated texts can sound awkward and lack the natural discourse style to make them not only easier to read, but interesting, too. The cultural context, descriptions, illustrations, and content can be inappropriate for the readers. Sometimes facts might be mistranslated. Therefore, care needs to be taken to ensure that the translation is accurate, clear, and natural. The following tips can help make translations snappy (lively, interesting, stimulating, or relevant). | ||
|
||
- Analyze the way this language and culture tell stories and other genres. Use those discourse forms when translating from another language. | ||
- Be ready to write several drafts and have each checked by (other) native speakers. Remember the wise saying by Robert Graves, "There is no such thing as good writing, only good rewriting." | ||
- Read the text to be translated several times before you begin, making sure you fully understand it yourself. | ||
- Do not translate word for word. Hear the words in your mind and let your writing flow from your thoughts. | ||
- The goal is not to merely translate what someone else has written, but to adapt the text to speak to your readers in their language. | ||
- If you get stuck trying to think of a word or phrase's meaning, take a break and try again later. | ||
- Read your translation aloud. You should be able to read it easily and naturally. | ||
- When translating dialogue, envision the character and write the words as they would be spoken by that personality. | ||
- Translating humor is challenging. Try reading the text aloud to others to discover if they find it humorous or not. If not, what might you do to make it so? | ||
- Rhyming and intonation do not translate well. Modify the text to express the ideas using the literary styles of the target language. | ||
- Before printing large quantities of the book, field-test the text and the illustrations with a variety of native speakers to check for understanding, ease of reading, naturalness, and interest. | ||
- Finally, be sure the title is snappy (attention-getting) in your language. |
This file contains 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
Oops, something went wrong.